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]
Date:   Sun, 24 Oct 2021 11:38:19 +0200
From:   Thomas Weißschuh <>
To:     Andy Lutomirski <>
Cc:     Christian Brauner <>,
        Linux API <>,
        Linux Kernel Mailing List <>,
        Luis Chamberlain <>,
        Jessica Yu <>
Subject: Re: [RFC] Expose request_module via syscall

On 2021-09-19 09:56+0200, Thomas Weißschuh wrote:
> On 2021-09-18T11:47-0700, Andy Lutomirski wrote:
> > But I admit I’m a bit confused.  What exactly is the container doing that causes the container’s copy of modprobe to be called?
> The container is running an instance of the docker daemon in swarm mode.
> That needs the "ip_vs" module (amongst others) and explicitly tries to load it
> via modprobe.

If somebody stumbles upon this specific issue:
The "ip_vs" module will be autoloaded in future kernel versions with

> > > If so the seccomp notifier can be used to intercept this system call for
> > > the container and verify the module against an allowlist similar to how
> > > we currently handle mount.
> > > 
> > > Christian

Powered by blists - more mailing lists