it also had an on-screen keyboard long story short, microsoft STILL hasn't fixed the vulnerability that let you escape into a shell in nt4
-
-
Replying to @whitequark @oshepherd and
you know the one where you go into some config, then open help, then open help file, then rightclick, then get explorer and free reign
3 replies 0 retweets 4 likes -
Replying to @whitequark @oshepherd and
it ran under admin rights so she renamed the acc to "ur a dick" and turned it off. a week later it was still off lol
2 replies 0 retweets 7 likes -
Replying to @whitequark @oshepherd and
New trick in Win10: right click start, Computer Management (nobody ever turns this off), Action -> Export List... gets you a file dialog.
2 replies 0 retweets 4 likes -
Replying to @gsuberland @whitequark and
Right click any directory and "Open in new window" gets you explorer. Go nuts.
2 replies 0 retweets 4 likes -
Replying to @gsuberland @oshepherd and
this is literally worse than x11 screensaver situation, which is a truly impressive feat considering how fucked x11 is
2 replies 0 retweets 8 likes -
Replying to @softfennec @whitequark and
No, The X screensaver situation is completely awful
1 reply 0 retweets 1 like -
Replying to @erincandescent @softfennec and
If your screensaver crashes your display unlocks. How many ways do you think there are to crash Gtk+ or Qt?
5 replies 3 retweets 4 likes -
Replying to @erincandescent @oshepherd and
Obvious solution: link screensaver and Xnest, run them as threads in the same process, run nothing but this under real X. :-)
1 reply 0 retweets 0 likes
Cleaner solution: ptrace screensaver process so it can't finish dying til tracer sees & acks it, have tracer kill X if screensaver dies.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.