Re: Stopping double clicking of a file
Re: Stopping double clicking of a file
- Subject: Re: Stopping double clicking of a file
- From: "Klaus L. Greulich" <email@hidden>
- Date: Wed, 4 Oct 2006 22:11:00 +0200
Hi!
Am 04.10.2006 um 21:47 schrieb development2:
Hi yourself,
On Oct 4, 2006, at 1:29 PM, Klaus L. Greulich wrote:
Hi!
Am 04.10.2006 um 21:14 schrieb development2:
Well never mind I thought Apple might make this kind of easy to
override.
Even if Apple would have made this (double-click) easy to
overrride, it would not help you.
Well you may be right there, I just needed a way to trap it so the
user can not open the file, without
going through our sanctioned method.
Well, now that I realize what you are talking about (took some
time ;-) )
I've also read the answer regarding the App delegate.
But what if the students try to open the file with a text editor or
vi or emacs or something like that?
Don't underestimate the ressourcefulness of your enem ... ahh ...
students.
It is just that your approach is - no offense - terribly wrong.
Hey that is really nice, given that you know nothing of how our app
works.
You have not provided much information about it. Or have I missed
something?
But to make it clear the
approach that I have asked about IS the proper way to go about it.
In my Humble Opinion, it is not.
Because there are other ways (or maybe other ways) to edit you
sensitive data than you application.
And if I imagine some student who wants to change something ...
You have to work with users and permissions.
Yeah permissions are already set up for users, but these students
can get on these teachers computers and they already have the
servers mounted and permissions set. So what do you do there, since
permissions are correct for that teacher?
Use password protection and encyption.
You have to direct them through a method of opening these files, so
that they can be authorized to use the file. The only way to do
that is make them go through some sanctioned way of opening these
files. That is what I am trying to do. I don't have to worry about
permissions the server takes care of that for me. I just have to
worry about making sure that the person who looks at these files
has access set up in our server software.
If you don't do that, your solution will be only some kind of
cosmetics, but not secure by any means.
If opening of ALL files goes through my sanctioned way of opening
files, then security is already taken care of.
But I will have to do something different in the app to fix this
properly.
In what app? As far as I understood you want the user not to be
able to double-click a file in the finder to open it?!?
What app are you referring to?
Im my app!! did I mention any other one???
In your original post you wrote:
"I need to turn off the ability to allow users to double click on a
file and have them open it up. There are security reasons for this,
as we do not want to allow students to open up the file and change
grades or attendance."
You didn't write: "and have them open it up *in my application*"
I thought you didn't want (for example) the students to open up a
restricted Word or Excel file via the Finder.
If it is your own application, securing sensitive information via
encryption should be not a problem, see Yojimbo.
klg
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden