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 21:52:47 +0200
Hi!
Am 04.10.2006 um 21:25 schrieb development2:
first of all, I am not talking about permissions. I am talking
about opening a file from the TEACHERS computer, if the student
gets on there with out there permission and they are already logged
into the server, then what do you do, since they already have the
proper permissions for all of these file, because they are logged
on properly.
Okay, that changes the situation a little bit.
The student can double click on the file and change there grades or
attendance or whatever and the teacher would not know.
Yes, I see your point.
But I also think your approach is wrong. Because students could
easily learn how to open a file via the terminal or other means.
My approach would be to store the information the students should not
access in an encrypted file.
Yojimbo is a good example how that could be achieved.
You can download it and test it here:
http://www.barebones.com/products/yojimbo/
I've bought it because even if someone gets his/her hands on my
computer while I'm away, my sensitive information is secure because
it is stored encrypted (256-bit, secure enough for me ;-) ) and
password-protected.
Every time I access sensitive information (for example: passwords,
sensitive data of projects I'm working on), I have to enter my
Yojimbo password.
That may sound inconvinient, but I think it is worth it.
You could do it this way, too.
Encrypt the data of the files you want to protect and have the
teacher to enter the password every time he/she accesses the file.
That approach would IMHO be far more secure than that what you had in
mind.
But - of course - your teachers have to be aware of security risks.
If you leave a door that should be locked, open, then you have a
problem ...
I am not worried about them accessing form a different computer,
because then that is a permission issue and that will all be set up
properly and the student will not even see it because they can't
get on the server.
Okay.
And if you say this does not happen, I will give you some email
address of teachers throughout the country that have experienced this.
Now that I know what you mean, I believe that. ;-)
I am trying to make sure that all class file access goes through
our sanctioned method of opening a file, that is all. If it does
everything works fine.
As I said, your approach is wrong, IMHO.
Of course, double-clicking is the most straight-forward thing to do.
But there are other means to open a file.
Another point: if students on a teacher's computer could not open a
file by any means, the teacher would also not be able to do it. That
is not what you want?
Why not provide the teacher(s) with a password to access the
restricted files?
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