Thanks for sending this out. This is a perfect example of what GUIs do to the brains of the brainless. This log, as with all other logs within Winblows, can be gotten to from the system shell. When the system has been de-commission and is no longer needed, the a person with proper access clearance could go and clear the log either with a text editor or by deleting the log file itself from the shell prompt.
In much the same way there are "clear log" buttons on error logs within windows that sys-admins want to have removed for the simple reason that someone who has created a security breach will want to cover their tracks. Or that they've been causing errors for reasons other than a security breach (I'm too dumb and I don't want anyone to know) will clear a log. So often I want to gain an understanding of what's been happening on a client's system and want to look at the logs. If they've cleared the logs all I can tell is when they cleared the logs. Sometimes I can figure out who cleared the logs, but only be seeing who was logged in at the time. However, anyone who's been to CU or any other decent school will know that if you walk away from your terminal without logging out, you'll be held responsible for what happed while you were logged in.
What aggravates such clarity (or lack thereof) many of us who have worked in the clerk's offices during local elections (and federal ones) know that few elections judges have their own log ins. They are issued a generic login that almost everyone else uses. So Joe Smith can clear records on a terminal that Jane Doe and five others are using as well and the sysop will never be able to figure out who actually cleared the log.
paul tiger
Evan Ravitz wrote:
http://blog.wired.com/27bstroke6/2009/03/ca-report-finds.html--
Join me on Facebook!
Purty pix and strange stories: Back to the Garden blog
Vote at Vote.org to take the "mock" out of democracy!
Evan Ravitz, founder. 303-440-6838
"Participation, that's the salvation of the human race."
-Pete Seeger
--
No virus found in this incoming message. Checked by AVG - www.avg.com Version: 8.0.237 / Virus Database: 270.11.8/1985 - Release Date: 03/05/09 07:54:00
