linux-kernel - Re: [PATCH] seccomp: dump core when using SECCOMP_RET

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]

Date:   Mon, 23 Jan 2017 09:10:25 +1100 (AEDT)
From:   James Morris <jmorris@...ei.org>
To:     Kees Cook <keescook@...omium.org>
cc:     Mike Frysinger <vapier@...too.org>,
        James Morris <james.l.morris@...cle.com>,
        LKML <linux-kernel@...r.kernel.org>,
        Andy Lutomirski <luto@...capital.net>,
        Will Drewry <wad@...omium.org>,
        Mike Frysinger <vapier@...omium.org>
Subject: Re: [PATCH] seccomp: dump core when using SECCOMP_RET_KILL

On Fri, 20 Jan 2017, Kees Cook wrote:

> Yup, I think this is fine. The additional kernel code executed before
> the do_exit() is relatively limited, and is equivalent to leaving
> kill(self, SIGSEGV) exposed in a seccomp filter. Setting an RLIMIT is
> also sufficient to block the core generation, so really paranoid
> environments can still do that.
> 
> The forwarded ack stands:
> 
> Acked-by: Kees Cook <keescook@...omium.org>
> 
> James, can you add this to your tree?

Mike, please resend the patch, I don't have it.


-- 
James Morris
<jmorris@...ei.org>