From: "J'raxis 270145" <gentoo@jraxis.org>
To: gentoo-security@lists.gentoo.org
Subject: Re: [gentoo-security] grsec kills xlock?!
Date: Tue, 1 Aug 2006 05:23:49 +0000 [thread overview]
Message-ID: <13361+19348!jraxis@iraxia64.local.jraxis.com> (raw)
In-Reply-To: <54684.70.28.241.91.1154386524.squirrel@webmail.confucius.ca>
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
next prev parent reply other threads:[~2006-08-01 5:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-31 22:55 [gentoo-security] grsec kills xlock?! Robert Paskowitz
2006-08-01 5:23 ` J'raxis 270145 [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-07-31 19:24 Alex Efros
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='13361+19348'\!'jraxis@iraxia64.local.jraxis.com' \
--to=gentoo@jraxis.org \
--cc=gentoo-security@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox