linux-kernel - Re: [PATCH] tty: prevent SAK to kill init process

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20101102085536.GB1871@jolsa.brq.redhat.com>
Date:	Tue, 2 Nov 2010 09:55:36 +0100
From:	Jiri Olsa <jolsa@...hat.com>
To:	"Eric W. Biederman" <ebiederm@...ssion.com>
Cc:	gregkh@...e.de, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] tty: prevent SAK to kill init process

On Mon, Nov 01, 2010 at 12:40:41PM -0700, Eric W. Biederman wrote:
> Jiri Olsa <jolsa@...hat.com> writes:
> 
> > hi,
> >
> > hitting "Secure Attention Key" on console that's openned
> > by init process, causing panic due to an attempt to kill
> > the init process.
> >
> > Fixing this by skipping the init process in the loop.
> 
> This sounds like proper behavior.  The goal of SAK is the guarantee that
> no one else has the tty one, and this violates that goal.  Which version
> init opens a controlling tty?  I expect it is time to deliver SIGCLUE
> to it.
I was using some older upstart version, which kept the console open

I found this log entry in changelog :)

       * No longer holds /dev/console open, so the SAK SysRq key will not
         kill Upstart.  (Bug: #486005)

So probably no need for the patch

sry for noise,
jirka
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/