Bug#428617: A possible approach
Adam Borowski
kilobyte at angband.pl
Sat Apr 17 11:37:44 UTC 2010
Wouldn't this approach work?:
set -e
gnome-screensaver &
loop `gnome-screensaver-command -q` until it says it's up and running (or a
timeout happens)
gnome-screensaver-command -l
exec gnome-session
I'm not sure I'm not missing something, but it appears to me there is
nothing an attacker could do. There's no keystroke that would allow taking
control; if Ctrl-C or Ctrl-Z work, they would merely stop the script and
abort the session. Of course, "appears" is not enough when discussing a
security issue, that's why it would be nice if someone more knowledgeable
could chime in.
With Gnome's startup taking longer than all of boot-up before gdm's prompt,
being able to press the "Power" button, go make some tea and return to see a
fully functional system would be a very nifty thing.
--
1KB // Microsoft corollary to Hanlon's razor:
// Never attribute to stupidity what can be
// adequately explained by malice.
More information about the pkg-gnome-maintainers
mailing list