Skip to contentSkip to conversation

iodine and SE Linux

DISCUSSION Russell Coker 3 participants 3 messages Jan 9, 2011 – Jan 12, 2011 SELinux security module

lore
Share & tools
lore
#0 lore raw

I notice that iodine (IP over DNS tunnel daemon) has sample SE Linux policy and a SE Linux patch to the source code.

The way it works is that you give iodine a -z parameter with the context that you want and it then calls setcon() to get it.

What I am thinking of doing is writing policy for iodine, icmptx, and any other daemon that operates in a similar manner that has an automatic domain transition and no setcon(). I am thinking of making this tunnel_t.

What do you think?

Signature · 8 lines
[email protected]
http://etbe.coker.com.au/          My Main Blog
http://doc.coker.com.au/           My Documents Blog

--
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 11 lines · Russell Coker

I notice that iodine (IP over DNS tunnel daemon) has sample SE Linux policy and a SE Linux patch to the source code.

The way it works is that you give iodine a -z parameter with the context that you want and it then calls setcon() to get it.

What I am thinking of doing is writing policy for iodine, icmptx, and any other daemon that operates in a similar manner that has an automatic domain transition and no setcon(). I am thinking of making this tunnel_t.

What do you think?

I'm not familiar with these tunnel services; does it make sense to adapt the existing stunnel policy? Or if we went to a tunnel_t generic service, would it be possible to get stunnel over to it?

Signature · 8 lines
Chris PeBenito
Tresys Technology, LLC
www.tresys.com | oss.tresys.com

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

Chris,

Perhaps a generic one may be best, as some of the custom protocols desired to be tunneled will not make it into a 'stunnel' discussion or forum. At least not in some places where we use the product.

Best, Hal
Sent via BlackBerry by AT&T

-----Original Message-----
From: "Christopher J. PeBenito" <[email protected]>
Sender: [email protected]
Date: Wed, 12 Jan 2011 15:12:46
To: <[email protected]>
Cc: SE-Linux<[email protected]>
Subject: Re: iodine and SE Linux

Quoted 11 lines · Russell Coker

I notice that iodine (IP over DNS tunnel daemon) has sample SE Linux policy and a SE Linux patch to the source code.

The way it works is that you give iodine a -z parameter with the context that you want and it then calls setcon() to get it.

What I am thinking of doing is writing policy for iodine, icmptx, and any other daemon that operates in a similar manner that has an automatic domain transition and no setcon(). I am thinking of making this tunnel_t.

What do you think?

I'm not familiar with these tunnel services; does it make sense to adapt the existing stunnel policy? Or if we went to a tunnel_t generic service, would it be possible to get stunnel over to it?

Signature · 15 lines
Chris PeBenito
Tresys Technology, LLC
www.tresys.com | oss.tresys.com

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



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