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
| ||
|
Message-ID: <97e88a06-4dfc-485c-b562-bed2a8e4b1b8@t-8ch.de> Date: Sun, 24 Oct 2021 11:38:19 +0200 From: Thomas Weißschuh <thomas@...ch.de> To: Andy Lutomirski <luto@...nel.org> Cc: Christian Brauner <christian.brauner@...ntu.com>, Linux API <linux-api@...r.kernel.org>, Linux Kernel Mailing List <linux-kernel@...r.kernel.org>, Luis Chamberlain <mcgrof@...nel.org>, Jessica Yu <jeyu@...nel.org> 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 https://lore.kernel.org/lkml/20211021130255.4177-1-linux@weissschuh.net/ applied. > > > 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