SELinux distro building

SELinux distro building

[Joshua Brindle]

Hi, I'm trying to set up support for SELinux in Gentoo linux (a source
based distro with a ports system for installing everything). Basically
instead of delivering a prepackaged/compiled SELinux build it downloads
and compiles right then and installs. The problems are numerous though
and I kinda wanted your advice
1) it installs to /usr/local/selinux which is unacceptable, it needs to
go to /usr/selinux (thats easily taken care of by patches to the
Makefiles which i already did)
2) when compiling the selinux archive it needs libsecure to already be
installed (and to have copied the .h files from the lsm kernel) before
the policy compiler can be built. This is a problem because the ports
system wants to compile everything, install it to a fake root so that it
can enumerate the files for uninstallation, then copy them to the file
system.
3) the Makefiles do not respect INSTALLPREFIX (which i also patched
for, but it's dirty) because we *must* install to the fake root before
installing to the filesystem, otherwise the sandbox kills it for
permissions (which is it supposed to do)

it seems to me that the entire archive package desperatly needs a
configure system so that it will be a little more flexible. What is your
opinion on this?
Also, i haven't looked at the debian builds since i don't have any
debian machines but how did you handle these problems, or did you? 

Thanks for any information you can give me.


Joshua Brindle
UNIX Administrator
Southern Nazarene University

--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.

SELinux distro building

[Joshua Brindle]

Hi, I'm trying to set up support for SELinux in Gentoo linux (a source
based distro with a ports system for installing everything). Basically
instead of delivering a prepackaged/compiled SELinux build it downloads
and compiles right then and installs. The problems are numerous though
and I kinda wanted your advice
1) it installs to /usr/local/selinux which is unacceptable, it needs to
go to /usr/selinux (thats easily taken care of by patches to the
Makefiles which i already did)
2) when compiling the selinux archive it needs libsecure to already be
installed (and to have copied the .h files from the lsm kernel) before
the policy compiler can be built. This is a problem because the ports
system wants to compile everything, install it to a fake root so that it
can enumerate the files for uninstallation, then copy them to the file
system.
3) the Makefiles do not respect INSTALLPREFIX (which i also patched
for, but it's dirty) because we *must* install to the fake root before
installing to the filesystem, otherwise the sandbox kills it for
permissions (which is it supposed to do)

it seems to me that the entire archive package desperatly needs a
configure system so that it will be a little more flexible. What is your
opinion on this?
Also, i haven't looked at the debian builds since i don't have any
debian machines but how did you handle these problems, or did you? 

Thanks for any information you can give me.


Joshua Brindle
UNIX Administrator
Southern Nazarene University

--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.

SELinux distro building

[Joshua Brindle]

Hi, I'm trying to set up support for SELinux in Gentoo linux (a source
based distro with a ports system for installing everything). Basically
instead of delivering a prepackaged/compiled SELinux build it downloads
and compiles right then and installs. The problems are numerous though
and I kinda wanted your advice
1) it installs to /usr/local/selinux which is unacceptable, it needs to
go to /usr/selinux (thats easily taken care of by patches to the
Makefiles which i already did)
2) when compiling the selinux archive it needs libsecure to already be
installed (and to have copied the .h files from the lsm kernel) before
the policy compiler can be built. This is a problem because the ports
system wants to compile everything, install it to a fake root so that it
can enumerate the files for uninstallation, then copy them to the file
system.
3) the Makefiles do not respect INSTALLPREFIX (which i also patched
for, but it's dirty) because we *must* install to the fake root before
installing to the filesystem, otherwise the sandbox kills it for
permissions (which is it supposed to do)

it seems to me that the entire archive package desperatly needs a
configure system so that it will be a little more flexible. What is your
opinion on this?
Also, i haven't looked at the debian builds since i don't have any
debian machines but how did you handle these problems, or did you? 

Thanks for any information you can give me.


Joshua Brindle
UNIX Administrator
Southern Nazarene University

--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.

Re: SELinux distro building

[Russell Coker]

On Tue, 12 Nov 2002 17:50, Joshua Brindle wrote:
> 1) it installs to /usr/local/selinux which is unacceptable, it needs to
> go to /usr/selinux (thats easily taken care of by patches to the
> Makefiles which i already did)

I think that autoconf would be good for this.  Also perhaps my script for 
extracting header files from the kernel patch (instead of from a kernel 
source tree) would be a good addition to the distribution.

> 2) when compiling the selinux archive it needs libsecure to already be
> installed (and to have copied the .h files from the lsm kernel) before
> the policy compiler can be built. This is a problem because the ports
> system wants to compile everything, install it to a fake root so that it
> can enumerate the files for uninstallation, then copy them to the file
> system.

I think it would be good to have the selinux-small split into two parts, one 
for the header files and library code for compiling applications, and the 
other for policy, run_init, etc.

> it seems to me that the entire archive package desperatly needs a
> configure system so that it will be a little more flexible. What is your
> opinion on this?

I agree.  Perhaps if I had posted patches here in the past rather than just 
talking about it then something would have happened.  I suggest that you post 
your patches here.

> Also, i haven't looked at the debian builds since i don't have any
> debian machines but how did you handle these problems, or did you?

Well I've got things basically solved for my use, but it is rather ugly.

-- 
http://www.coker.com.au/selinux/   My NSA Security Enhanced Linux packages
http://www.coker.com.au/bonnie++/  Bonnie++ hard drive benchmark
http://www.coker.com.au/postal/    Postal SMTP/POP benchmark
http://www.coker.com.au/~russell/  My home page


--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.

Re: SELinux distro building

[Joshua Brindle]

>I think that autoconf would be good for this.  Also perhaps my script
for 
>extracting header files from the kernel patch (instead of from a
kernel 
>source tree) would be a good addition to the distribution.

I agree, thats pretty much what i was thinking about. I can't even
imagine trying to distribute code to the public without a configure
system. If someone is more familiar with autoconf and the basic build
process of selinux than me then i'd be very gracious if they worked on
this

>I think it would be good to have the selinux-small split into two
parts, one 
>for the header files and library code for compiling applications, and
the 
>other for policy, run_init, etc.

EXACTLY!. the libs have to be installed before the policy compiler
anyway, they should be 2 separate packages. Either that, or
selinux-small should know how to link to libs in it's own directory
before being installed, a single package with several "install" steps
isn't a clean implementation, and makes distro packaging a pain.

>I agree.  Perhaps if I had posted patches here in the past rather than
just 
>talking about it then something would have happened.  I suggest that
you post 
>your patches here.

My patches are basically hacked INSTALLPREFIX and fixed paths into the
Makefile, it is clearly not something that would be helpful, autoconf
would be much better.



Joshua Brindle
UNIX Administrator
Southern Nazarene University

--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.

Re: SELinux distro building

[Brad Chapman]

--- Joshua Brindle <JBrindle@snu.edu> wrote:
> >I think that autoconf would be good for this.  Also perhaps my script
> for 
> >extracting header files from the kernel patch (instead of from a
> kernel 
> >source tree) would be a good addition to the distribution.
> 
> I agree, thats pretty much what i was thinking about. I can't even
> imagine trying to distribute code to the public without a configure
> system. If someone is more familiar with autoconf and the basic build
> process of selinux than me then i'd be very gracious if they worked on
> this

I agree. Having an autoconf-based configure system for SELinux would be
wonderful, and it would make changing options and adding features to the libs,
progs, etc a snap. Does anyone know how to use autoconf and all its friends?

> 
> >I think it would be good to have the selinux-small split into two
> parts, one 
> >for the header files and library code for compiling applications, and
> the 
> >other for policy, run_init, etc.
> 
> EXACTLY!. the libs have to be installed before the policy compiler
> anyway, they should be 2 separate packages. Either that, or
> selinux-small should know how to link to libs in it's own directory
> before being installed, a single package with several "install" steps
> isn't a clean implementation, and makes distro packaging a pain.

Yup. That's another problem that I've had to put up with. If I had the time,
I would code this up and test it, but I don't :(

> 
> >I agree.  Perhaps if I had posted patches here in the past rather than
> just 
> >talking about it then something would have happened.  I suggest that
> you post 
> >your patches here.
> 
> My patches are basically hacked INSTALLPREFIX and fixed paths into the
> Makefile, it is clearly not something that would be helpful, autoconf
> would be much better.

Post them anyway. I might try them. 

> 
> 
> 
> Joshua Brindle
> UNIX Administrator
> Southern Nazarene University
> 

Brad

__________________________________________________
Do you Yahoo!?
U2 on LAUNCH - Exclusive greatest hits videos
http://launch.yahoo.com/u2

--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.

Re: SELinux distro building

[Brian May]

On Tue, Nov 12, 2002 at 04:50:09PM -0800, Brad Chapman wrote:
> I agree. Having an autoconf-based configure system for SELinux would be
> wonderful, and it would make changing options and adding features to the libs,
> progs, etc a snap. Does anyone know how to use autoconf and all its friends?

I am confident I could do this, or at least create an initial
version anyway.

Would somebody be willing to test a patch that does this?
--
Brian May <bam@snoopy.apana.org.au>

--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.

Re: SELinux distro building

[Joshua Brindle]

>Would somebody be willing to test a patch that does this?

ooh ooh pick me

what I personally need is something that can configure the whole
package or 2 separate ones to install into a INSTALLPREFIX that can then
be copied to the live filesystem, and also, it _must_ be able to be
installed in /usr/selinux rather than /usr/local.. if you can do the
conjfigure stuff i'll be glad to test


--
Brian May <bam@snoopy.apana.org.au>

Joshua Brindle
UNIX Administrator
Southern Nazarene University

--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.

Re: SELinux distro building

[Brian May]

On Wed, Nov 13, 2002 at 12:31:23PM +1100, Brian May wrote:
> Would somebody be willing to test a patch that does this?

I have modified Russell's version of libselinux-small,
to build with autoconf/automake/libtool.

See
<URL:http://www.microcomaustralia.com.au/debian/selinux-small-2002102211.tar.gz>

This mainly involved creating configure.in, AUTHORS, NEWS and
**/Makefile.am, but I had to change some source code too (most noteably
module/checkpolicy/policy_scan.l to reflect the new name of
policy_parse.h and utils/spasswd to reflect the fact that automake
doesn't appear to allow compiling the same source code multiple times
with different compile time options).

I am highly confident that some things will still be broken ;-)

-----------
What works:
-----------

make distcheck (this does some pretty strict tests; for instance to make
sure no files are missing and that it can build the object files in
another directory)


make install prefix=....

where prefix is the place to install.

-----------
What sort of works:
-----------

--with-lsm=dir can be used to change path to LSM directory, but
directory must be a full directory name, relative directories names
will break.

-----------
What doesn't work:
-----------

debian/rules not updated.

Makefile in top level source directory totally replaced.

devfsd-se.so will go into the wrong directory by default (anyone know
how get automake to put plugin modules in the correct directory?)

devfsd-se.so is linked with libsecure.a, as per previous build setup.
This is broken; it means the shared library has code in it that
wasn't compiled with PIC. However, it is not possible to compile
libselinux with PIC (position independent code); the compiler
complains with an error:

gcc -DHAVE_CONFIG_H -I. -I. -I../.. -I../../libsecure/include -Wall -g
-O2 -Wp,-MD,.deps/security.pp -c security.c -fPIC -DPIC -o
.libs/security.lo security.c: In function `security': security.c:5:
Invalid `asm' statement: security.c:5: fixed or forbidden register 3
(bx) was spilled for class BREG. make[3]: *** [security.lo] Error 1

For now we can get away with using non-PIC code on i386; it might be a
major problem on other platforms though.

MLS support has been completely ommited; it should be easy to add
though.

AUTHORS and NEWS are empty files.

-----------
What should work but I haven't checked:
-----------

Does everything get installed in the correct place?

Does anything get installed that shouldn't be installed?

Are any files from the source archive missing?
--
Brian May <bam@snoopy.apana.org.au>

--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.

Re: SELinux distro building

[Brian May]

On Wed, Nov 13, 2002 at 07:29:03PM +1100, Brian May wrote:
> On Wed, Nov 13, 2002 at 12:31:23PM +1100, Brian May wrote:
> > Would somebody be willing to test a patch that does this?
> 
> I have modified Russell's version of libselinux-small,
> to build with autoconf/automake/libtool.
> 
> See
> <URL:http://www.microcomaustralia.com.au/debian/selinux-small-2002102211.tar.gz>

Has anyone tested this?

Not that I intend to push anybody, I am just curious if the silence
means that everyone has missed this message or tried it and had no
problems...
--
Brian May <bam@snoopy.apana.org.au>

--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.

Re: SELinux distro building

[Brian May]

On Wed, Nov 13, 2002 at 07:29:03PM +1100, Brian May wrote:

I have updated this file:

> <URL:http://www.microcomaustralia.com.au/debian/selinux-small-2002102211.tar.gz>

It should now be able to include the LSM include files correctly.

Also, the configure script will now do a simple check to ensure that the
LSM directory given is correct.
--
Brian May <bam@snoopy.apana.org.au>

--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.

Re: SELinux distro building

[Joshua Brindle]

much closer
i used --with-lsm=/usr/src/linux-2.4.19-selinux because it was looking
in ../../.. for lsm-2.4, instead of just ../ (i dunno)
anyway, it compiled almost everything then i got this error
(if you prefer i can pipe the entire compile to a file and attach..
Thanks


rm -f libsecure.a
ar cru libsecure.a accept_secure.o avc_enforcing.o avc_toggle.o chsid.o
chsidfs.o connect_secure.o context.o execle_secure.o execlp_secure.o
execl_secure.o execve_secure.o execvp_secure.o execv_secure.o fchsid.o
fchsidfs.o fstatfs_secure.o fstat_secure.o get_default_type.o
getosecsid.o getpeername_secure.o getsecsid.o get_sid_list.o
getsockname_secure.o get_user_sid.o helpers.o ichsid.o lchsid.o
listen_secure.o lstat_secure.o mkdir_secure.o mknod_secure.o
msgget_secure.o msgrcv_secure.o msgsid.o msgsnd_secure.o open_secure.o
popen_secure.o query_user_sid.o recvfrom_secure.o recvmsg_secure.o
security.o security_change_sid.o security_compute_av.o
security_context_to_sid.o security_get_sids.o security_get_user_sids.o
security_load_policy.o security_member_sid.o security_mls.o
security_notify_perm.o security_sid_to_context.o
security_transition_sid.o semget_secure.o semsid.o sendmsg_secure.o
sendto_secure.o shmget_secure.o shmsid.o socket_secure.o statfs_secure.o
stat_secure.o symlink_secure.o 
ranlib libsecure.a
make[3]: Leaving directory
`/root/selinux-new/selinux-small-2002102211/libsecure/src'
Making all in test
make[3]: Entering directory
`/root/selinux-new/selinux-small-2002102211/libsecure/test'
gcc -DHAVE_CONFIG_H -I. -I. -I../.. -I../../libsecure/include  -Wall 
-g -O2 -c avc_enforcing.c
avc_enforcing.c: In function `main':
avc_enforcing.c:8: warning: implicit declaration of function `printf'
avc_enforcing.c:12: warning: implicit declaration of function
`avc_enforcing'
avc_enforcing.c:21: warning: implicit declaration of function `perror'
/bin/sh ../../libtool --mode=link gcc  -g -O2  -o avc_enforcing 
avc_enforcing.o  ../../libsecure/src/libsecure.a 
mkdir .libs
gcc -g -O2 -o avc_enforcing avc_enforcing.o 
../../libsecure/src/libsecure.a
gcc -DHAVE_CONFIG_H -I. -I. -I../.. -I../../libsecure/include  -Wall 
-g -O2 -c avc_toggle.c
avc_toggle.c: In function `main':
avc_toggle.c:8: warning: implicit declaration of function `printf'
avc_toggle.c:12: warning: implicit declaration of function
`avc_toggle'
avc_toggle.c:21: warning: implicit declaration of function `perror'
/bin/sh ../../libtool --mode=link gcc  -g -O2  -o avc_toggle 
avc_toggle.o  ../../libsecure/src/libsecure.a 
gcc -g -O2 -o avc_toggle avc_toggle.o  ../../libsecure/src/libsecure.a
gcc -DHAVE_CONFIG_H -I. -I. -I../.. -I../../libsecure/include  -Wall 
-g -O2 -c chsid.c
In file included from chsid.c:1:
../../libsecure/include/fs_secure.h:9:31: linux/flask/flask.h: No such
file or directory
In file included from chsid.c:1:
../../libsecure/include/fs_secure.h:14: parse error before
"security_id_t"
../../libsecure/include/fs_secure.h:18: parse error before
"security_id_t"
../../libsecure/include/fs_secure.h:23: parse error before
"security_id_t"
../../libsecure/include/fs_secure.h:27: parse error before
"security_id_t"
../../libsecure/include/fs_secure.h:30: parse error before
"security_id_t"
../../libsecure/include/fs_secure.h:34: parse error before
"security_id_t"
../../libsecure/include/fs_secure.h:37: parse error before
"security_id_t"
../../libsecure/include/fs_secure.h:40: parse error before
"security_id_t"
../../libsecure/include/fs_secure.h:43: parse error before
"security_id_t"
../../libsecure/include/fs_secure.h:47: parse error before
"security_id_t"
../../libsecure/include/fs_secure.h:53: parse error before
"security_id_t"
../../libsecure/include/fs_secure.h:56: parse error before
"security_id_t"
../../libsecure/include/fs_secure.h:59: parse error before
"security_id_t"
../../libsecure/include/fs_secure.h:90: parse error before
"security_id_t"
../../libsecure/include/fs_secure.h:94: parse error before
"security_id_t"
In file included from chsid.c:2:
../../libsecure/include/ss.h:4:34: linux/flask/syscalls.h: No such file
or directory
../../libsecure/include/ss.h:5:31: linux/flask/flask.h: No such file or
directory
In file included from chsid.c:2:
../../libsecure/include/ss.h:16: warning: `struct security_response'
declared inside parameter list
../../libsecure/include/ss.h:16: warning: its scope is only this
definition or declaration, which is probably not what you want
../../libsecure/include/ss.h:16: warning: `struct security_query'
declared inside parameter list
../../libsecure/include/ss.h:18: parse error before "ssid"
../../libsecure/include/ss.h:23: parse error before "ssid"
../../libsecure/include/ss.h:28: parse error before "ssid"
../../libsecure/include/ss.h:33: parse error before "ssid"
../../libsecure/include/ss.h:38: parse error before "sid"
../../libsecure/include/ss.h:42: warning: type defaults to `int' in
declaration of `security_context_t'
../../libsecure/include/ss.h:42: parse error before "scontext"
../../libsecure/include/ss.h:47: parse error before "__u32"
../../libsecure/include/ss.h:49: parse error before '*' token
../../libsecure/include/ss.h:52: parse error before "fromsid"
../../libsecure/include/ss.h:64: parse error before
"string_to_security_class"
../../libsecure/include/ss.h:64: warning: type defaults to `int' in
declaration of `string_to_security_class'
../../libsecure/include/ss.h:64: warning: data definition has no type
or storage class
../../libsecure/include/ss.h:66: parse error before "tclass"
chsid.c: In function `main':
chsid.c:7: `security_id_t' undeclared (first use in this function)
chsid.c:7: (Each undeclared identifier is reported only once
chsid.c:7: for each function it appears in.)
chsid.c:7: parse error before "sid"
chsid.c:11: warning: implicit declaration of function `printf'
chsid.c:15: `sid' undeclared (first use in this function)
chsid.c:17: warning: implicit declaration of function `strlen'
chsid.c:20: warning: implicit declaration of function `perror'
make[3]: *** [chsid.o] Error 1
make[3]: Leaving directory
`/root/selinux-new/selinux-small-2002102211/libsecure/test'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory
`/root/selinux-new/selinux-small-2002102211/libsecure'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory
`/root/selinux-new/selinux-small-2002102211'
make: *** [all-recursive-am] Error 2

>>> Brian May <bam@snoopy.apana.org.au> 11/19/02 07:37PM >>>
On Wed, Nov 13, 2002 at 07:29:03PM +1100, Brian May wrote:

I have updated this file:

>
<URL:http://www.microcomaustralia.com.au/debian/selinux-small-2002102211.tar.gz>

It should now be able to include the LSM include files correctly.

Also, the configure script will now do a simple check to ensure that
the
LSM directory given is correct.
--
Brian May <bam@snoopy.apana.org.au>

--
This message was distributed to subscribers of the selinux mailing
list.
If you no longer wish to subscribe, send mail to
majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.

--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.

Re: SELinux distro building

[Brian May]

On Wed, Nov 20, 2002 at 02:54:18PM -0600, Joshua Brindle wrote:
> much closer
> i used --with-lsm=/usr/src/linux-2.4.19-selinux because it was looking
> in ../../.. for lsm-2.4, instead of just ../ (i dunno)
> anyway, it compiled almost everything then i got this error
> (if you prefer i can pipe the entire compile to a file and attach..
> Thanks

Looks like another directory that needs to include LSM directories.

What directories need these include files?

So far it seems to be:

libsecure/src
libsecure/test
modules/checkpolicy

Is that all? Are there any others I might have missed?
-- 
Brian May <bam@snoopy.apana.org.au>

--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.

Re: SELinux distro building

[Joshua Brindle]

ok, here is a list of places that need $(MODDIR)/include added to
INCLUDES in Makefile
libsecure/test
setfiles/
utils/newrole
utils/run_init
utils/spasswd
devfsd/

after adding all these it compiled cleanly on a completely virgin
system. excellent.. Thanks

Joshua Brindle
UNIX Administrator
Southern Nazarene University

>>> Brian May <bam@snoopy.apana.org.au> 11/20/02 04:48PM >>>
On Wed, Nov 20, 2002 at 02:54:18PM -0600, Joshua Brindle wrote:
> much closer
> i used --with-lsm=/usr/src/linux-2.4.19-selinux because it was
looking
> in ../../.. for lsm-2.4, instead of just ../ (i dunno)
> anyway, it compiled almost everything then i got this error
> (if you prefer i can pipe the entire compile to a file and attach..
> Thanks

Looks like another directory that needs to include LSM directories.

What directories need these include files?

So far it seems to be:

libsecure/src
libsecure/test
modules/checkpolicy

Is that all? Are there any others I might have missed?
-- 
Brian May <bam@snoopy.apana.org.au>

--
This message was distributed to subscribers of the selinux mailing
list.
If you no longer wish to subscribe, send mail to
majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.

--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.