[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20201026162228.7f2d16a0@kicinski-fedora-PC1C0HJN.hsd1.ca.comcast.net>
Date: Mon, 26 Oct 2020 16:22:28 -0700
From: Jakub Kicinski <kuba@...nel.org>
To: James Morris <jmorris@...ei.org>
Cc: Jeff Vander Stoep <jeffv@...gle.com>,
"David S. Miller" <davem@...emloft.net>,
linux-security-module@...r.kernel.org,
Roman Kiryanov <rkir@...gle.com>, netdev@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH] vsock: use ns_capable_noaudit() on socket create
On Tue, 27 Oct 2020 07:37:37 +1100 (AEDT) James Morris wrote:
> On Fri, 23 Oct 2020, Jeff Vander Stoep wrote:
>
> > During __vsock_create() CAP_NET_ADMIN is used to determine if the
> > vsock_sock->trusted should be set to true. This value is used later
> > for determing if a remote connection should be allowed to connect
> > to a restricted VM. Unfortunately, if the caller doesn't have
> > CAP_NET_ADMIN, an audit message such as an selinux denial is
> > generated even if the caller does not want a trusted socket.
> >
> > Logging errors on success is confusing. To avoid this, switch the
> > capable(CAP_NET_ADMIN) check to the noaudit version.
> >
> > Reported-by: Roman Kiryanov <rkir@...gle.com>
> > https://android-review.googlesource.com/c/device/generic/goldfish/+/1468545/
> > Signed-off-by: Jeff Vander Stoep <jeffv@...gle.com>
>
> Reviewed-by: James Morris <jamorris@...ux.microsoft.com>
Applied to net, thanks!
Powered by blists - more mailing lists