Skip to contentSkip to conversation

chattr

DISCUSSION Russell Coker 3 participants 4 messages Jul 12, 2002 SELinux security module

lore
Share & tools
lore
#0 lore raw

It seems that chattr depends on the "write" permission and that lsattr depends on the "read" permission. I think that they should depend on "setattr" and "getattr" permissions respectively.

[email protected] pointed out that it is possible to chattr /tmp on my SE play machine, "chattr +i /tmp /var/tmp /var/tmp/*" would be rather annoying...

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.

--
You have received this message because you are subscribed to the selinux 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 7 lines · Russell Coker

It seems that chattr depends on the "write" permission and that lsattr depends on the "read" permission. I think that they should depend on "setattr" and "getattr" permissions respectively.

[email protected] pointed out that it is possible to chattr /tmp on my SE play machine, "chattr +i /tmp /var/tmp /var/tmp/*" would be rather annoying...

I'm not sure I understand. At least for ext2 and ext3, chattr calls ioctl with a EXT[23]_IOC_SETFLAGS command, and SELinux performs a setattr permission check in its selinux_file_ioctl hook for this command. The ext2 and ext3 filesystem code also performs capability checks for setting flags on files that are not owned by the process (the fowner capability permission) and for changing the immutable or append-only flags (the linux_immutable capability permission). chattr +i /tmp fails for user_t on my systems.

--
Stephen D. Smalley, NAI Labs
[email protected]

--
You have received this message because you are subscribed to the selinux 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

sshd

Hi,
Before installing selinux, I used to have sshd running. However,
with current selinux, sshd seems to refuse starting and response following message

Privilege separation user sshd does not exist

Has anyone encounter similiar problem? Can you give me a hand on this?

Thanks in advance,
Simon

--
You have received this message because you are subscribed to the selinux list. If you no longer wish to subscribe, send mail to [email protected] with the words "unsubscribe selinux" without quotes as the message.

#3 lore raw

Re: sshd

Quoted 7 lines · Simon Han

Before installing selinux, I used to have sshd running. However,
with current selinux, sshd seems to refuse starting and response following message

Privilege separation user sshd does not exist

Has anyone encounter similiar problem? Can you give me a hand on this?

Read selinux/utils/openssh-3.4p1/README.privsep. This isn't specific to SELinux; the sshd pseudo user is needed by the privilege separation support in the new OpenSSH version.

--
Stephen D. Smalley, NAI Labs
[email protected]

--
You have received this message because you are subscribed to the selinux list. If you no longer wish to subscribe, send mail to [email protected] with the words "unsubscribe selinux" without quotes as the message.