Mailing List Archive: grsec kills xlock?!

grsec kills xlock?!

Jul 31, 2006, 12:24 PM

Post #1 of 3 (1797 views)

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. :)

--
WBR, Alex.
--
gentoo-security@gentoo.org mailing list

Re: grsec kills xlock?! [ In reply to ]

r2d2 at gentoo

Jul 31, 2006, 3:55 PM

Post #2 of 3 (1732 views)

Permalink

> 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

--
gentoo-security@gentoo.org mailing list

Re: grsec kills xlock?! [ In reply to ]

gentoo at jraxis

Jul 31, 2006, 10:23 PM

Post #3 of 3 (1730 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@gentoo.org> wrote:

> Date: Mon, 31 Jul 2006 18:55:24 -0400 (EDT)
> From: Robert Paskowitz <r2d2@gentoo.org>
> Reply-to: gentoo-security@lists.gentoo.org
> Subject: Re: [gentoo-security] grsec kills xlock?!
> To: gentoo-security@lists.gentoo.org
> Message-ID: <54684.70.28.241.91.1154386524.squirrel@webmail.confucius.ca>
> 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@gentoo.org mailing list