You have the same worry of a DBA writing the root password on a post it note. In every organization, there has to be some level of trust. Tell the DBA to use Linux, there's a lock icon to enable the screensaver in most X environments. ;-) Thank you, Micah Gersten onShore Networks Internal Developer http://www.onshore.com Philip Thompson wrote: > > I understand what you're saying, but I don't completely agree with > this. What happens when the DBA has a table of names and SSNs on > screen and then gets up from his desk to run to the bathroom? In the > fear that he may ruin is best slacks (err, jeans), he forgets to close > the DB viewer or lock his desktop. Mr. ShouldntBeInHere walks by, sees > the monitor of data and takes a picture with his new iPhone 3G and > keeps walking. Well, now he just grabbed 50 names and SSNs. Uh oh! > > Now, I understand that Mr. DBA should be held responsible for not > taking the necessary precautions to make sure that no one else got to > his database. However, if the database had been encrypted, then maybe, > just maybe those names wouldn't have been exploited. But, in an effort > to make sure that he is taking all the necessary precautions, > shouldn't he have encrypted his database as well? > > > Also, there was this same question last Friday (I think) about > encrypting DBs. Search the archives and/or ask a MySQL list. > > But to not be a complete jerk... I use AES. > > ~Philip > -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
