For reasons that are not particularly interesting, I found myself reading the XScreensaver FAQ last night, which answers the question, “The unlock dialog is funny looking, why not use GTK?” That led me to JWZ’s mini-rant On Toolkits, which reminded me of this ancient vulnerability in the OS X screensaver where you could unlock the screen by typing 1280 characters in the password dialog. I remember reading about it at the time, but I never really understood how people found bugs like this until I had kids.
§
Or cats, for that matter.
The ironic thing is, after reading those jwz links and replacing the KDE screensaver with Xscreensaver as per the instructions in the FAQ, I locked the session, deliberately entered the wrong password a few times, and wound up–and I swear this is the truth–crashing Xscreensaver and reclaiming the desktop.
Did you file a bug?
— Mark ![]()
frag frag bugtrack.bbs not found on true=no°!x—r… Pretty shure zes/no ash trez kaz kez yyyy y n nnnn plus alot of parking space$444..free……???????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????
I’ll see your comment, and raise you an “overflow:hidden”.
— Mark ![]()
I am no longer accepting public comments on this post, but you can use this form to contact me privately. (Your message will not be published.)
§
firehose ‧ code ‧ music ‧ planet
© 2001–8 Mark Pilgrim