linux-kernel - Re: [RFC] Expose request

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: <b7390542-ea4a-de12-7567-734f6dbf488d@kernel.org>
Date:   Fri, 24 Sep 2021 16:04:39 -0700
From:   Andy Lutomirski <luto@...nel.org>
To:     Christian Brauner <christian.brauner@...ntu.com>
Cc:     Luis Chamberlain <mcgrof@...nel.org>,
        Thomas Weißschuh <thomas@...ch.de>,
        Linux API <linux-api@...r.kernel.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Jessica Yu <jeyu@...nel.org>
Subject: Re: [RFC] Expose request_module via syscall

On 9/24/21 06:19, Christian Brauner wrote:
> On Wed, Sep 22, 2021 at 01:06:49PM -0700, Andy Lutomirski wrote:

> I just meant that the programs in the container can see the modules
> available on the host. Simplest thing could be bind-mounting in the
> host's module folder with suitable protection (locked read-only mount).
> But yeah, it can likely be as simple as allowing it to ask for a module
> and not bother telling it about what is available.
> 

If the container gets to see host modules, interesting races when 
containers are migrated CRIU-style will result.