bugtraq - Re: COSEINC Linux Advisory #1: Linux Kernel Parent Process Death Signal Vulnerability

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: <Pine.LNX.4.44.0708180031280.7714-100000@D00M.lightwave.net.ru>
Date: Sat, 18 Aug 2007 00:35:40 +0400 (MSD)
From: Dan Yefimov <dan@...5.lightwave.net.ru>
To: Nicolas Rachinsky <bugtraq-0@...turing-complete.org>
Cc: bugtraq@...urityfocus.com
Subject: Re: COSEINC Linux Advisory #1: Linux Kernel Parent Process Death
 Signal Vulnerability

On Fri, 17 Aug 2007, Nicolas Rachinsky wrote:

> * Dan Yefimov <dan@...5.lightwave.net.ru> [2007-08-17 05:27 +0400]:
> > BTW, SIGKILL and SIGSTOP can be issued by an O_ASYNC file I/O also (look in 
> > fcntl(2) at F_SETSIG section). If you use F_SETSIG for sending SIGKILL or 
> > SIGSTOP, there's nothing to be done with that - that behaviour is well 
> 
> Looking in that man page I see:
>        F_GETSIG and F_SETSIG are Linux-specific.
> 
And we consider Linux too. But anyway, they're unexploitable since signals set 
with F_SETSIG are subject to usual permission checks.
-- 

    Sincerely Your, Dan.