Skip to contentSkip to conversation

experimental SEDebian 2.5 packages

DISCUSSION Colin Walters 2 participants 3 messages Jul 19, 2003 – Jul 28, 2003 SELinux security module

lore
Share & tools
lore
#0 lore raw

Hi,

I've created Debian packages of the SELinux 2.5 bits, and my policy. This is still experimental, please don't deploy it on production systems. That being said, most of it seems to work for me, and I can boot in enforcing mode with a base Debian installation.

Before you install these; note that I doubt I am going to have time to continuously keep up with all the rapid changes that happen in Debian unstable. This means you have to be very careful when upgrading to ensure that a .selinux package isn't removed. I recommend you put all the .selinux packages on hold after you've installed them.

In summary, while I'm interested in hearing feedback on these packages, if you are new to SELinux, and especially if you are not an experienced Debian user, I recommend you stick with Linux 2.4 and Russell's packages for now (http://www.coker.com.au/selinux).

With all that out of the way: Just put the following in your /etc/apt/sources.list:

deb http://web.verbum.org/debian/ experimental/

(The above URI will probably change once these packages stop being experimental).

At least today, doing a simple apt-get upgrade should get you the .selinux versions of everything except coreutils; one solution to this is to go into aptitude and select the .selinux version of coreutils manually. I'll try to upgrade to the latest coreutils later today, but again I can't guarantee that I'll be able to track sid, so please double-check that you have the .selinux versions installed.

Comments appreciated!

--
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
In reply to Tom
Quoted 10 lines · Tom
Quoted 5 lines · Colin Walters

Before you install these; note that I doubt I am going to have time to continuously keep up with all the rapid changes that happen in Debian unstable. This means you have to be very careful when upgrading to ensure that a .selinux package isn't removed. I recommend you put all the .selinux packages on hold after you've installed them.

This, btw. is true for all of them. Well, at least for sid which is moving rapidly, but also for woody you can not GUARANTEE that a security fix doesn't replace the package.

Yeah.

Quoted 3 lines

If you want me to set up a mirror for this like I did for Russel and Brian, just tell me how to best fetch them (rsync-over-ssh or something). I'd be happy to do it.

I have set up a regular rsync server, to copy the debs you can do e.g.:

rsync -av web.verbum.org::web/debian/experimental/ /path/to/mirror/

Of course, running rsyncd required writing a policy for it :) That should be attached. I had to create a shell script /usr/sbin/rsyncd which looks like:

#!/bin/sh -e
exec rsync --daemon

rsyncd.{te,fc} are in my arch tree too.

#DESC rsyncd - rsync daemon
#
# Author: Colin Walters <[email protected]>

type rsyncd_port_t, port_type;

daemon_domain(rsyncd)

# Allow the sysadmin to exec the server directly. At least

# rsyncd on Debian does not have an init script.
role sysadm_r types rsyncd_t;
domain_auto_trans(sysadm_t, rsyncd_exec_t, rsyncd_t)

base_file_read_access(rsyncd_t) r_dir_file(rsyncd_t, { etc_t etc_runtime_t resolv_conf_t }) dontaudit rsyncd_t proc_t:file r_file_perms; can_network(rsyncd_t)

# Allow rsyncd to be a shell script which execs /usr/bin/rsync --daemon can_exec(rsyncd_t, bin_t)

allow rsyncd_t rsyncd_port_t:tcp_socket name_bind;
allow rsyncd_t self:{ unix_stream_socket unix_dgram_socket } create_socket_perms;

allow rsyncd_t self:capability { setuid setgid net_bind_service };

# rsyncd
/usr/sbin/rsyncd		system_u:object_r:rsyncd_exec_t
#1 lore raw
In reply to Colin Walters
Quoted 5 lines · Colin Walters

Before you install these; note that I doubt I am going to have time to continuously keep up with all the rapid changes that happen in Debian unstable. This means you have to be very careful when upgrading to ensure that a .selinux package isn't removed. I recommend you put all the .selinux packages on hold after you've installed them.

This, btw. is true for all of them. Well, at least for sid which is moving rapidly, but also for woody you can not GUARANTEE that a security fix doesn't replace the package.

I've found it a good idea to put them on hold for all debian releases.

Quoted 7 lines

With all that out of the way: Just put the following in your /etc/apt/sources.list:

deb http://web.verbum.org/debian/ experimental/

(The above URI will probably change once these packages stop being experimental).

If you want me to set up a mirror for this like I did for Russel and Brian, just tell me how to best fetch them (rsync-over-ssh or something). I'd be happy to do it.

Signature · 8 lines
http://web.lemuria.org/pubkey.html
pub  1024D/2D7A04F5 2002-05-16 Tom Vogt <[email protected]>
     Key fingerprint = C731 64D1 4BCF 4C20 48A4  29B2 BF01 9FA1 2D7A 04F5

--
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.