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] [day] [month] [year] [list]
Date:	Fri, 5 Jun 2015 20:50:45 +0900
From:	'Greg Kroah-Hartman' <gregkh@...uxfoundation.org>
To:	Namjae Jeon <namjae.jeon@...sung.com>
Cc:	'Kay Sievers' <kay@...y.org>, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 2/3] driver: core: add security labels to devtmpfs

On Fri, Jun 05, 2015 at 08:15:55PM +0900, Namjae Jeon wrote:
> > On Fri, Jun 05, 2015 at 07:10:23PM +0900, Namjae Jeon wrote:
> > > Add support for setting security labels(e.g. smack or selinux labels) to
> > > devtmpfs device nodes. In this manner, drivers can specify desired security
> > > label in their device_type->devnode or class->devnode method.
> > 
> > What driver wants to do this?  And how does it determine the proper
> > security label from within the kernel?  Isn't that something that only
> > userspace can know/set properly?
> Yes, It is possible by userspace, But This api change will help to set uid/gid
> and xattr values easily without need of complex userspace scripts in absence of
> udev like helper.

If you want to do things like this, use a "complex" userspace script
like Android has for their startup (hint, it's just a tiny bash script,
nothing "complex" about it at all...)

> And security label that decided as per each embedded system will be set by
> this api in driver.

Exactly how will that happen?  I don't see any users of it.

greg k-h
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ