LWN: Comments on "X.org screensaver bypass found" https://lwn.net/Articles/476134/ This is a special feed containing comments posted to the individual LWN article titled "X.org screensaver bypass found". en-us Mon, 22 Sep 2025 05:52:02 +0000 Mon, 22 Sep 2025 05:52:02 +0000 https://www.rssboard.org/rss-specification lwn@lwn.net *whew* https://lwn.net/Articles/477505/ https://lwn.net/Articles/477505/ etrusco <div class="FormattedComment"> I wonder who would use a bleeding edge distro while needing a stable system with shared physical access?<br> </div> Fri, 27 Jan 2012 01:20:38 +0000 X.org screensaver bypass sponsored by Canonical https://lwn.net/Articles/477461/ https://lwn.net/Articles/477461/ daniels <div class="FormattedComment"> Thanks for the random drive-by abuse, but I haven't been a part of or contributed anything to Ubuntu since I left Canonical over six years ago.<br> </div> Thu, 26 Jan 2012 22:26:01 +0000 X.org screensaver bypass found https://lwn.net/Articles/477458/ https://lwn.net/Articles/477458/ gvy <div class="FormattedComment"> You must have had bothered to mark the change clearly in the code commit *you* made -- and must have had communicated that to the others working on it as well.<br> <p> It's not "oh well". It's why six-month-craze is counterproductive.<br> <p> #include &lt;stdflame/ubuntu&gt;<br> </div> Thu, 26 Jan 2012 22:19:15 +0000 X.org screensaver bypass found https://lwn.net/Articles/477457/ https://lwn.net/Articles/477457/ gvy <a rel="nofollow" href="http://www.cyberciti.biz/tips/my-10-unix-command-line-mistakes.html#comment-169179">This blogpost</a> has some discussion of that kind of fun... Thu, 26 Jan 2012 22:13:46 +0000 X.org screensaver bypass sponsored by Canonical https://lwn.net/Articles/477456/ https://lwn.net/Articles/477456/ gvy <div class="FormattedComment"> Yes, Daniel Stone of Ubuntu took care of screwing up for the others. Thank you, Dan.<br> </div> Thu, 26 Jan 2012 22:06:22 +0000 X.org screensaver bypass found https://lwn.net/Articles/476644/ https://lwn.net/Articles/476644/ sebas <div class="FormattedComment"> That's actually two issues TuxOnIce solved quite nicely: smarter and faster preparation of the hibernate process, and showing progress while doing it (and also being able to cancel it while it's hibernating).<br> <p> I haven't tried it in a while though. It used to be very reliable for me, but nowadays, I'm just using S3.<br> </div> Mon, 23 Jan 2012 10:07:23 +0000 Fedora 16 fix already rushed to stable. https://lwn.net/Articles/476633/ https://lwn.net/Articles/476633/ gilboa <div class="FormattedComment"> As the title suggests.<br> Quick yum update + login/logout is very-much-advised.<br> <p> - Gilboa<br> </div> Mon, 23 Jan 2012 07:21:15 +0000 X.org screensaver bypass found https://lwn.net/Articles/476332/ https://lwn.net/Articles/476332/ zzxtty <div class="FormattedComment"> You want to remove both KPMU and KPDV.<br> </div> Fri, 20 Jan 2012 13:41:04 +0000 X.org screensaver bypass found https://lwn.net/Articles/476325/ https://lwn.net/Articles/476325/ v13 <div class="FormattedComment"> Quick hack:<br> <p> xkbcomp :0 - &gt; /tmp/koko.map<br> <p> vi /tmp/koko.map<br> <p> ... remove the Multiply thingy that causes this ...<br> <p> xkbcomp /tmp/koko.map :0<br> <p> <p> </div> Fri, 20 Jan 2012 12:35:36 +0000 X.org screensaver bypass found https://lwn.net/Articles/476297/ https://lwn.net/Articles/476297/ Pawlerson <div class="FormattedComment"> According to Phoronix you're safe with the current Kubuntu/Ubuntu. :)<br> </div> Fri, 20 Jan 2012 09:19:43 +0000 X.org screensaver bypass found https://lwn.net/Articles/476292/ https://lwn.net/Articles/476292/ rvfh <div class="FormattedComment"> Does not seem to affect my Kubuntu 11.10 machine... or am I missing something?<br> Ctrl Alt (keypad)* correct? Does nothing on my locked machine.<br> </div> Fri, 20 Jan 2012 08:49:29 +0000 X.org screensaver bypass found https://lwn.net/Articles/476265/ https://lwn.net/Articles/476265/ whot <div class="FormattedComment"> fwiw, I've posted a summary of the issue, its history and its effects, here:<br> <p> <a href="http://who-t.blogspot.com/2012/01/xkb-breaking-grabs-cve-2012-0064.html">http://who-t.blogspot.com/2012/01/xkb-breaking-grabs-cve-...</a><br> </div> Fri, 20 Jan 2012 03:44:39 +0000 X.org screensaver bypass found https://lwn.net/Articles/476250/ https://lwn.net/Articles/476250/ Kit <div class="FormattedComment"> I don't believe I'm using TuxOnIce, it doesn't appear that's what Fedora uses based on a quick search. It spends the time on preallocating space for the image (the exact wording is slightly different)... it would be nice if it at least had some sort of progress indicator. The part where it's actually dumping the memory to disk doesn't take close to as long.<br> </div> Fri, 20 Jan 2012 02:05:39 +0000 X.org screensaver bypass found https://lwn.net/Articles/476243/ https://lwn.net/Articles/476243/ nix <blockquote> On Linux, I only use hibernate, because suspend still isn't reliable for me... unfortunately, this takes upwards of 10 minutes to shut the machine down </blockquote> That sounds like a bug. When you say 'hibernate', do you mean the hibernate script that is part of TuxOnIce? If so, you might want to mention it on one of the tuxonice lists, and see if there's anything that can be done to speed things up. My 12Gb two-disk machine takes under a minute to suspend. Fri, 20 Jan 2012 01:14:48 +0000 X.org screensaver bypass found https://lwn.net/Articles/476241/ https://lwn.net/Articles/476241/ daniels <div class="FormattedComment"> This is now fixed with xkeyboard-config 2.5: <a href="http://listserv.bat.ru/xkb/Message/8375.html">http://listserv.bat.ru/xkb/Message/8375.html</a><br> </div> Fri, 20 Jan 2012 00:57:35 +0000 X.org screensaver bypass found https://lwn.net/Articles/476224/ https://lwn.net/Articles/476224/ mgedmin You mean this version of hw/xfree86/dixmods/xkbPrivate.c doesn't handle Private(type=0x86, data="clsgrab"), so there's no harm of that action existing in my xkb config? Now it makes sense to me. Thu, 19 Jan 2012 22:43:34 +0000 X.org screensaver bypass found https://lwn.net/Articles/476217/ https://lwn.net/Articles/476217/ Kit <div class="FormattedComment"> <font class="QuotedText">&gt; Do people still run screensavers? That's pretty irresponsible. </font><br> <font class="QuotedText">&gt; The monitor should be turned off, and most of the box too.</font><br> <p> I don't run a screen saver on any machine to 'save the screen' or 'provide pretty pictures when I'm not there'.<br> <p> On Windows, my screen saver starts up (blank) at the same time as the system is set to shut off the monitor. Attempting to wake up the system after this time results in being presented with the lock screen, which runs in a different desktop context than the desktop itself. I'll suspend the system if I'm going to be away for more than a couple minutes and don't have anything running that'll be aversely affected by being paused (i.e. no active network operations).<br> <p> On OSX, the situation is largely the same. Lock screen presented upon resume, and set to suspend very aggressively (a suspend/resume cycle is incredibly short).<br> <p> On Linux, I only use hibernate, because suspend still isn't reliable for me... unfortunately, this takes upwards of 10 minutes to shut the machine down. When it comes back up, it has the screen saver running as a lock screen, to require the user to enter a password before they can actually use the machine. I really hate using the screen saver as the screen "lock", it's very sluggish to start and even worse to bring up the password box (if it's been idle for at least a few minutes, /10 seconds/ to show the box isn't unusual). It's also hard to tell when the resume has finished with the blank screen saver (I can't tell if it's showing the screen saver or if it's still resuming), so I might end up having to actually install and use a screen saver that actually shows something. Certainly the worst of the three for me.<br> </div> Thu, 19 Jan 2012 22:26:25 +0000 X.org screensaver bypass found https://lwn.net/Articles/476222/ https://lwn.net/Articles/476222/ pabs <div class="FormattedComment"> Thats because this screen combo appears to kill gnome-screensaver at least. One would hope such screenlockers detect a stuff going away and re-aquire grabs etc.<br> </div> Thu, 19 Jan 2012 22:23:54 +0000 X.org screensaver bypass found https://lwn.net/Articles/476212/ https://lwn.net/Articles/476212/ nteon <div class="FormattedComment"> this affects the 'lock screen' function in gnome-shell on my fedora 16 box, so its not just screensavers<br> </div> Thu, 19 Jan 2012 21:29:10 +0000 X.org screensaver bypass found https://lwn.net/Articles/476209/ https://lwn.net/Articles/476209/ thyrsus <div class="FormattedComment"> This is present in Fedora 16. In my experience, after using it once, the screen lock refuses to start again until I log out and back in.<br> <p> </div> Thu, 19 Jan 2012 21:00:16 +0000 *whew* https://lwn.net/Articles/476189/ https://lwn.net/Articles/476189/ dskoll <p>Running Debian Squeeze and X.Org 1.7.7. Glad not to be on bleeding-edge :) Thu, 19 Jan 2012 20:06:39 +0000 X.org screensaver bypass found https://lwn.net/Articles/476170/ https://lwn.net/Articles/476170/ daniels <div class="FormattedComment"> It's meant to be a debugging aid for app and toolkit developers, who need to break stuck grabs from time to time. It wasn't meant to be enabled by default, but that apparently got lost in a miscommunication between myself and the keyboard layout maintainer, and I didn't think to double-check afterwards. Oh well.<br> <p> <a href="http://lists.x.org/archives/xorg-devel/attachments/20120119/bcfd3bb3/attachment.bin">http://lists.x.org/archives/xorg-devel/attachments/201201...</a> is the recommended patch.<br> </div> Thu, 19 Jan 2012 19:38:43 +0000 X.org screensaver bypass found https://lwn.net/Articles/476171/ https://lwn.net/Articles/476171/ __alex <div class="FormattedComment"> Unless like me you use the xorg-edgers ppa in which case you definitely are vulnerable :(<br> </div> Thu, 19 Jan 2012 19:36:11 +0000 X.org screensaver bypass found https://lwn.net/Articles/476161/ https://lwn.net/Articles/476161/ theophrastus <div class="FormattedComment"> sweet_zombie_jesus! (and here all this time i was typing in my password to get back in like a chump [wink]) can someone explain what proper function this 'feature' was intended to serve ...debugging backdoor? [looks down at keyboard and wonders about all the other possible ctrl-alt-strange_keys]<br> </div> Thu, 19 Jan 2012 18:57:10 +0000 X.org screensaver bypass found https://lwn.net/Articles/476160/ https://lwn.net/Articles/476160/ zwenna <div class="FormattedComment"> Ubuntu 11.10 still has xserver 1.10, so is not vulnerable.<br> </div> Thu, 19 Jan 2012 18:43:17 +0000 X.org screensaver bypass found https://lwn.net/Articles/476158/ https://lwn.net/Articles/476158/ mgedmin <div class="FormattedComment"> Hm, I see the XF86ClearGrab binding is active in my 'xkbcomp :0 -' output on Ubuntu 11.10 (both the mapping and the interpret bits), and I can see XF86ClearGrab show up in xev output, but when I press it when the screensaver is active, nothing happens. Huh?<br> </div> Thu, 19 Jan 2012 18:30:50 +0000 X.org screensaver bypass found https://lwn.net/Articles/476155/ https://lwn.net/Articles/476155/ prometheanfire <div class="FormattedComment"> Bunch of people use this at work,<br> <p> Already changed their background and put a new screensaver up (with a custom message). Who said bugs can't be fun :D<br> </div> Thu, 19 Jan 2012 18:24:23 +0000 X.org screensaver bypass found https://lwn.net/Articles/476147/ https://lwn.net/Articles/476147/ ncm <div class="FormattedComment"> Do people still run screensavers? That's pretty irresponsible. The monitor should be turned off, and most of the box too.<br> <p> But this is really about automatic time-out screen locking, and authentication. We're still at a very primitive stage there. Arguably the machine should give you library-PC features with no authentication, and then enable more features as it gains confidence that it's really you. Passwords would be just a way to speed that up. To recognize keyboard timing signatures would give enough security, by itself, for almost everything.<br> </div> Thu, 19 Jan 2012 17:57:49 +0000 Never really worked that well https://lwn.net/Articles/476144/ https://lwn.net/Articles/476144/ epa <div class="FormattedComment"> The X screen locking has always been a bit flaky. On a heavily loaded machine, it might take several seconds between invoking 'xlock' and the screen becoming locked - the screen is not locked while the fancy graphics are set up.<br> </div> Thu, 19 Jan 2012 17:29:51 +0000 X.org screensaver bypass found https://lwn.net/Articles/476138/ https://lwn.net/Articles/476138/ Kit Wow, now that's pretty unsettling.<br /> <br /> Simply throwing a window up over the other windows has bothered me for several years (ever since the first time I saw GAIM open a window <i>over</i> a locked screen saver!). It seemed like a hack just to have something (sort of like the login screen on Windows 9x, where clicking 'cancel' would log you in anyways!).<br /> <br /> Obviously a determined attacker with physical access will be able to eventually bypass any protection... but one would at least hope that the measures in place would be enough to defeat the casual walker-byer! Thu, 19 Jan 2012 17:03:43 +0000