Skip to contentSkip to conversation

ssh policy

DISCUSSION Russell Coker 1 participant 1 message Jul 31, 2002 SELinux security module

lore
Share & tools
lore
#0 lore raw

I've put a new archive of my SE Linux policy on
http://www.coker.com.au/selinux/policy.tgz (no debs yet because I'm still experimenting with it).

The major change I've just made is merging ssh.te and sshd.te. The reason for this is that they both require access to ~/.ssh, this means that to support one without the other makes the policy more complex but delivers little benefit. There are few people who want to run ssh without sshd (or the other way around). Also I believe that having the files separate will result in someone deciding that they don't want ssh and removing ssh.te but not /usr/bin/ssh! This would result in /usr/bin/ssh running in user_t thus being marginally less secure.

While these issues are both minor, I think it's enough reason for us as policy developers to save ourselves the extra effort and merge the files.

Also it's just occurred to me that I should create a new domain for ssh-keygen to give an automatic transition of key files {identity,id_rsa,id_dsa}{,.pub} to a type that can't be read by sshd. I had previously thought of just using a different type for the identity, id_dsa, and id_rsa files, but I realised that sshd has no cause to read the .pub files (although I don't think there's any real need to deny read access either).

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.