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] [thread-next>] [day] [month] [year] [list]

Message-ID: <m1zktszvba.fsf@fess.ebiederm.org>
Date:	Mon, 01 Nov 2010 12:40:41 -0700
From:	ebiederm@...ssion.com (Eric W. Biederman)
To:	Jiri Olsa <jolsa@...hat.com>
Cc:	gregkh@...e.de, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] tty: prevent SAK to kill init process

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.

Eric
--
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/