gentoo at jraxis
Jul 31, 2006, 10:23 PM
Post #3 of 3
(636 views)
Permalink
|
Try xscreensaver instead of xlock:
http://www.jwz.org/xscreensaver/versus-xlock.html
> In XLock, all the display modes run in the same process that is locking
> the screen. This means that if any of those programs has a bug, all of
> XLock will crash. When XLock crashes, your screen unlocks. And
> obviously, a lock that can spontaneously unlock itself is not a very
> good lock...
At 2006-07-31T22:55:24+0000, <r2d2 [at] gentoo> wrote:
> Date: Mon, 31 Jul 2006 18:55:24 -0400 (EDT)
> From: Robert Paskowitz <r2d2 [at] gentoo>
> Reply-to: gentoo-security [at] lists
> Subject: Re: [gentoo-security] grsec kills xlock?!
> To: gentoo-security [at] lists
> Message-ID: <54684.70.28.241.91.1154386524.squirrel [at] webmail>
> User-Agent: SquirrelMail/1.4.6
>
> > Hi!
> >
> > Looks like some of screensavers used in xlock conflict with hardened:
> >
> > 2006-07-31_19:07:03.64042 kern.alert: grsec: signal 11 sent to
> > /usr/bin/xlock[xl
> > ock:24135] uid/euid:1000/1000 gid/egid:100/100, parent
> > /usr/bin/fluxbox[fluxbox:
> > 8403] uid/euid:1000/1000 gid/egid:100/100
> >
> > This happens only once for now.
> >
> >
> > P.S. It's very funny anyway: one security feature kills other. :)
> >
>
> FAQ #1: http://www.grsecurity.net/wiki/index.php/GrsecurityFAQ
--
J'raxis 270145
http://www.jraxis.com/
--
gentoo-security [at] gentoo mailing list
|
