ipsec access to { sysadm_tty_device_t sysadm_devpts_t }
I have been having some discussions with Steve about access to { sysadm_tty_device_t sysadm_devpts_t }. We agree that giving all daemons access to the administrator terminal is a bad idea in concept.
However some programs seem to require it. The PCMCIA cardmgr program does not seem to start correctly unless it has such access.
Now I'm working on ipsec which seems to require { read write ioctl getattr } access to those device types for correct functioning. As I am just learning about IPSec I'm not in a good position to analyse this in detail, could someone who knows it better please have a look and see if there's something that can be done about it or whether it really needs such access.
Signature · 3 lines
I do not get viruses because I do not use MS software. If you use Outlook then please do not put my email address in your address-book so that WHEN you get a virus it won't use my address in the
Quoted 1 line
From field.
--
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.
Russell Coker <[email protected]>:
Quoted 5 lines
I have been having some discussions with Steve about access to {
sysadm_tty_device_tsysadm_devpts_t}. We agree that giving all daemons access to the administrator terminal is a bad idea in concept.
Quoted 8 lines
However some programs seem to require it. The PCMCIA cardmgr program does not seem to start correctly unless it has such access.
Now I'm working on ipsec which seems to require { read write ioctl getattr } access to those device types for correct functioning. As I am just learning about IPSec I'm not in a good position to analyse this in detail, could someone who knows it better please have a look and see if there's something that can be done about it or whether it really needs such access.
Slightly OT/side question:
Which IPSec implementation are you starting with - NIST reference, Free/swan or a completely new one?
-------------------------------------------------------------------------
Jesse I Pollard, II
Email: [email protected]
Any opinions expressed are solely my own.
--
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.
Quoted 8 lines · Jesse Pollard
Russell Coker <[email protected]>:
Quoted 2 lines
Now I'm working on ipsec which seems to require { read write ioctl getattr } access to those device types for correct functioning. As I am
Slightly OT/side question:
Which IPSec implementation are you starting with - NIST reference, Free/swan or a completely new one?
I'm using Free/swan, I wasn't aware that I had a choice. Could you please give us a brief analysis of the difference between the different versions?
Signature · 3 lines
I do not get viruses because I do not use MS software. If you use Outlook then please do not put my email address in your address-book so that WHEN you get a virus it won't use my address in the
Quoted 1 line
From field.
--
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.
--------- Received message begins Here ---------
Quoted 6 lines · Jesse Pollard
Quoted 4 lines
Russell Coker <[email protected]>:
Quoted 2 lines
Now I'm working on ipsec which seems to require { read write ioctl getattr } access to those device types for correct functioning. As I am
Quoted 7 lines
Quoted 4 lines
Slightly OT/side question:
Which IPSec implementation are you starting with - NIST reference, Free/swan or a completely new one?
I'm using Free/swan, I wasn't aware that I had a choice. Could you please give us a brief analysis of the difference between the different versions?
I don't know that there really is one. The NIST web page shows updates as of 2000. I also had looked at Freeswan a year ago, and saw several reports that it wouldn't get included in the kernel due to "unapproved" coding practices (quotes mine - they also may have cleaned up since then too).
Since both NIST and the NSA were working on related things (and how the freeswan project wasn't interested in US involment) I was curious about any merging of interest between the two groups.
I'm interested in data labeling being passed with network packets (including user identity...) but don't get much time to do anything on it.
-------------------------------------------------------------------------
Jesse I Pollard, II
Email: [email protected]
Any opinions expressed are solely my own.
--
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.
Quoted 4 lines · Russell Coker
I have been having some discussions with Steve about access to {
sysadm_tty_device_tsysadm_devpts_t}. We agree that giving all daemons access to the administrator terminal is a bad idea in concept.
Quoted 8 lines
However some programs seem to require it. The PCMCIA cardmgr program does not seem to start correctly unless it has such access.
Now I'm working on ipsec which seems to require { read write ioctl getattr } access to those device types for correct functioning. As I am just learning about IPSec I'm not in a good position to analyse this in detail, could someone who knows it better please have a look and see if there's something that can be done about it or whether it really needs such access.
I would expect that the IKE daemon would not need such access, so that if we put it into a separate domain from the IPSEC utilities, we could refrain from granting such access to that domain. But I haven't tried this yet.
--
Stephen D. Smalley, NAI Labs
[email protected]
--
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.