linux-kernel - Re: [PATCH] emit logging when a process receives a fatal signal

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: <Pine.LNX.4.61.0611182030360.10940@yvahk01.tjqt.qr>
Date:	Sat, 18 Nov 2006 20:31:50 +0100 (MET)
From:	Jan Engelhardt <jengelh@...ux01.gwdg.de>
To:	Folkert van Heusden <folkert@...heusden.com>
cc:	Mikael Pettersson <mikpe@...uu.se>, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] emit logging when a process receives a fatal signal


>> 4. If this is about detecting the loss of specific processes
>>    (network services say), then the problem can be solved in
>>    user-space by using a separate monitor process, or by
>>    controlling the processes via ptrace.
>
>No not only for specific processes. It helps you detect problems with
>processes you dind't know they have bugs and flakey hardware (sig 11).

Write an LSM module that hooks ->task_kill. It's probably the most 
beautiful and non-intrusive solution in the set of possible solutions.



	-`J'
-- 
-
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/