Re: Code Security

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Ethan,
It seems like you're looking for a programmatic solution to a physical
security problem. In the end, your most viable solution will likely
be to train Mr. Goodguy to remove the key the same way he needs to
remember his ATM card after a withdrawal. I've seen programmatic
work-arounds to solve similar issues, but they have always ended up
being significantly arduous for the end users...
Respectfully,
Joshua D. Arneson
-----Original Message-----From: Ethan Rosenberg
[mailto:erosenberg@xxxxxxxxxxxxxxxxxxxx] Sent: Friday, February 13,
2015 9:12 AMTo: php-db@xxxxxxxxx.netSubject: Re: [PHP-DB] Code
Security
On 02/13/2015 02:58 AM, Karl DeSaulniers wrote:> Prevent THIS from
ever happening.>> On Feb 12, 2015, at 11:03 PM, Ethan Rosenberg
wrote:>>> He asks Mr.[naive]Nice if he could look at the computer
while it is logged in.>>> Otherwise, I would say an external key that
has a salt stored on it that the user has to insert in the computer
before the system can be accessed.> Like an access key card. Immediate
shut down when tampered and/or removed.>> Just a stab in the dark
though.>> Best,>> Karl DeSaulniers> Design Drumm
Karl -
Thanks.
The key is already plugged in. Mr [Naive] Nice is using the computer,
and is logged in. Mr. Ugly just want to "look at" the computer.
Ethan--
Joshua -
My apologies for an HTML message.  That is all I have at work.

How about this -
Block access to Ctrl-Alt-Del for Mr. Nice. 
TIA
Ethan



[Index of Archives]     [PHP Home]     [PHP Users]     [Postgresql Discussion]     [Kernel Newbies]     [Postgresql]     [Yosemite News]

  Powered by Linux