linux-kernel - Re: [PATCH] SELinux - support mls categories for context mounts

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 28 Sep 2006 12:45:39 -0700
From:	Andrew Morton <akpm@...l.org>
To:	James Morris <jmorris@...ei.org>
Cc:	linux-kernel@...r.kernel.org, Stephen Smalley <sds@...ho.nsa.gov>,
	Cory Olmo <colmo@...stedCS.com>
Subject: Re: [PATCH] SELinux - support mls categories for context mounts

On Thu, 28 Sep 2006 15:30:53 -0400 (EDT)
James Morris <jmorris@...ei.org> wrote:

> This patch allows commas to be embedded into context mount options (i.e. 
> "-o context=some_selinux_context_t"), to better support multiple 
> categories, which are separated by commas and confuse mount.
> 
> For example, with the current code:
> 
>   mount -t iso9660 /dev/cdrom /media/cdrom -o \
>   ro,context=system_u:object_r:iso9660_t:s0:c1,c3,c4,exec
> 
> The context option that will be interpreted by SELinux is
> context=system_u:object_r:iso9660_t:s0:c1
> 
> instead of
> context=system_u:object_r:iso9660_t:s0:c1,c3,c4
> 
> The options that will be passed on to the file system will be
> ro,c3,c4,exec.
> 
> The proposed solution is to allow/require the SELinux context option 
> specified to mount to use quotes when the context contains a comma.

None of this seems to be documented anywhere.  I expect the people who
actually work on this stuff make a pretty tight group, but...
-
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/