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: <61a720eb.1c69fb81.80210.02b6@mx.google.com>
Date:   Wed, 1 Dec 2021 07:14:50 +0000
From:   CGEL <cgel.zte@...il.com>
To:     Christian Brauner <christian.brauner@...ntu.com>
Cc:     dbueso@...e.de, jamorris@...ux.microsoft.com,
        keescook@...omium.org, ktkhai@...tuozzo.com, legion@...nel.org,
        linux-kernel@...r.kernel.org, ran.xiaokai@....com.cn,
        varad.gautam@...e.com
Subject: Re: [PATCH V2] ipc: add set_ownership() and permissions() callbacks
 for posix mqueue sysctl

On Mon, Oct 04, 2021 at 12:53:13PM +0200, Christian Brauner wrote:
> On Thu, Sep 16, 2021 at 01:49:31AM +0000, CGEL wrote:
> > esOn Mon, Sep 13, 2021 at 04:40:47PM +0200, Christian Brauner wrote:
> > > On Fri, Aug 27, 2021 at 03:12:06AM -0700, CGEL wrote:
> > > > From: Ran Xiaokai <ran.xiaokai@....com.cn>
> > > > 
> > > > When a non-root user process creates a user namespace and ipc namespace
> > > > with command "unshare -Ur -i", and map the root user inside
> > > > the user namesapce to the global owner of user namespace.
> > > > The newly created user namespace OWNS the ipc namespace,
> > > > So the root user inside the user namespace should have full access
> > > > rights to the ipc namespace resources and should be writable to
> > > > the ipc mqueue sysctls.
> > > > 
> > > > v2:
> > > >   - update commit msg.
> > > >   - fix the coding style issue.
> > > > Signed-off-by: Ran Xiaokai <ran.xiaokai@....com.cn>
> > > > ---
> > > 
> > > David,
> > > 
> > > are you happy with this too? If so I'd pick this up.
> > > 
> > 
> > Hi Christian,
> > 
> > Is there a xx-next branch for this kind patch?
> > We will try to fixes other issues like this, so we could tag the follow-up
> > patches with the branch name.
> 
> Hm, sorry that message slipped through the pre-mid-and post-conference
> cracks.  I'll added the patches now for testing. See:
> 
> https://git.kernel.org/pub/scm/linux/kernel/git/brauner/linux.git/log/?h=kernel.fixes
> 
> Christian

Hi Christian,

How the the testing goes on? 

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ