Skip to contentSkip to conversation

SELinux Policy compiler doesn't like leading numbers in fs names

DISCUSSION Daniel J Walsh 2 participants 3 messages Jan 12, 2011 SELinux security module

lore
Share & tools
lore
#0 lore raw

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

https://bugzilla.redhat.com/show_bug.cgi?id=668871

Is there any logical reason for this or is this just a bug? -----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/

iEYEARECAAYFAk0t9LwACgkQrlYvE4MpobOnqACg4Hj22Ioqgopb96HTvJ0ZkrmO 02gAnAlpIDBLjSTQkoOvah/S535YePCM
=65GT
-----END PGP SIGNATURE-----

--
This message was distributed to subscribers of the selinux mailing list. If you no longer wish to subscribe, send mail to [email protected] with the words "unsubscribe selinux" without quotes as the message.

#1 lore raw
Quoted 6 lines · Daniel J Walsh

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

https://bugzilla.redhat.com/show_bug.cgi?id=668871

Is there any logical reason for this or is this just a bug?

The filesystem name for a genfscon statement happens to be specified as an identifier and an identifier must begin with a letter, but I don't think that there is any technical reason for the restriction.

Would we want to allow all identifiers to be able to start with alphanumeric characters (or maybe even "_") or just filesystem names?

Quoted 13 lines

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/

iEYEARECAAYFAk0t9LwACgkQrlYvE4MpobOnqACg4Hj22Ioqgopb96HTvJ0ZkrmO 02gAnAlpIDBLjSTQkoOvah/S535YePCM
=65GT
-----END PGP SIGNATURE-----

--
This message was distributed to subscribers of the selinux mailing list. If you no longer wish to subscribe, send mail to [email protected] with the words "unsubscribe selinux" without quotes as the message.

Signature · 8 lines
James Carter <[email protected]>
National Security Agency


--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to [email protected] with
the words "unsubscribe selinux" without quotes as the message.
#2 lore raw

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Quoted 13 lines · James Carter

On Wed, 2011-01-12 at 13:36 -0500, Daniel J Walsh wrote:
https://bugzilla.redhat.com/show_bug.cgi?id=668871

Is there any logical reason for this or is this just a bug?

Quoted 8 lines

The filesystem name for a genfscon statement happens to be specified as an identifier and an identifier must begin with a letter, but I don't think that there is any technical reason for the restriction.

Would we want to allow all identifiers to be able to start with alphanumeric characters (or maybe even "_") or just filesystem names?

- --
This message was distributed to subscribers of the selinux mailing list. If you no longer wish to subscribe, send mail to [email protected] with
the words "unsubscribe selinux" without quotes as the message.

I would say allow any alphanumeric and _, and then let the refpolicy guidelines control what gets into that policy. Forcing IBM to change the name of their file system for SELinux seems a little nuts. -----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/

iEYEARECAAYFAk0t+hUACgkQrlYvE4MpobMT2gCeMA/lLDF4bv1+rgNesFlHR42P fIEAn06YCwRWmIrtjAvJIhwT+uQbOCfU
=L6cW
-----END PGP SIGNATURE-----

--
This message was distributed to subscribers of the selinux mailing list. If you no longer wish to subscribe, send mail to [email protected] with the words "unsubscribe selinux" without quotes as the message.