Your message dated Sun, 18 Apr 2010 16:59:19 +0200
with message-id <20100418145919.ga9...@patate.is-a-geek.org>
and subject line Re: Bug#562884: xscreensaver can be killed with Alt+SysRq+F
has caused the Debian Bug report #562884,
regarding xscreensaver can be killed with Alt+SysRq+F
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
562884: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=562884
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: xscreensaver
Version: 4.24-5
Severity: grave
Tags: security
Justification: user security hole
Hi,
I'm a bit new to this bugreporting stuff. I have however discovered that it
is possible to kill xscreensaver with Alt+SysRq+F (if this function is not
disabled). This may comprimise security when xscreensaver-command is used
with the -lock option, because the screen will be unlocked.
gnome-screensaver seems not to be vulnerable to this attack.
--- End Message ---
--- Begin Message ---
On Mon, Dec 28, 2009 at 20:41:53 +0100, Lars Olav Dybsjord wrote:
> Package: xscreensaver
> Version: 4.24-5
> Severity: grave
> Tags: security
> Justification: user security hole
>
> Hi,
>
> I'm a bit new to this bugreporting stuff. I have however discovered that it
> is possible to kill xscreensaver with Alt+SysRq+F (if this function is not
> disabled). This may comprimise security when xscreensaver-command is used
> with the -lock option, because the screen will be unlocked.
>
> gnome-screensaver seems not to be vulnerable to this attack.
>
>
Closing this for the same reason as 564080. I don't think this is a bug
in the screensavers, let alone a RC bug.
The Debian kernel disables some sysrq functions by default now,
including this one (it sets the sysrq mask to 0x01b6).
If people still feel that the screensaver should do something more, then
this bug can be reopened at a lower severity IMO.
Cheers,
Julien
signature.asc
Description: Digital signature
--- End Message ---
