linux-kernel - Re: Potentially undesirable interactions between vfork() and time namespaces

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: <CANaxB-yhmfRru4+n_+Q39QpkTzZjBHqkoq3JFwAG9mXDd0bjKA@mail.gmail.com>
Date:   Sun, 11 Sep 2022 15:51:41 -0700
From:   Andrei Vagin <avagin@...il.com>
To:     Kees Cook <keescook@...omium.org>
Cc:     Christian Brauner <brauner@...nel.org>,
        "Eric W. Biederman" <ebiederm@...ssion.com>,
        Alexey Izbyshev <izbyshev@...ras.ru>,
        Florian Weimer <fweimer@...hat.com>,
        Dmitry Safonov <0x7f454c46@...il.com>,
        linux-kernel@...r.kernel.org, linux-mm@...ck.org
Subject: Re: Potentially undesirable interactions between vfork() and time namespaces

On Sun, Sep 11, 2022 at 8:12 AM Kees Cook <keescook@...omium.org> wrote:
>
> On Fri, Sep 09, 2022 at 09:51:58AM +0200, Christian Brauner wrote:
> > As stated above the proposed exec behavior we currently clearly emulate
> > in userspace. So that part is fine.
>
> It's not clear to me yet what the right solution is from this thread so
> far... what's needed for v6.0 release (since we're quickly running out
> of release candidates)?

Kees,

I think we reached a consensus to go with Eric's idea. We will send
the patch shortly.

Thanks,
Andrei