Skip to contentSkip to conversation

This does not look correct....

DISCUSSION [email protected] 4 participants 4 messages Jul 4, 2002 – Jul 5, 2002 SELinux security module

lore
Share & tools
lore
#0 lore raw

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hello,

I know I have not been trying to configure SELinux for very long, but this does not look correct to me. Should ssh have a getty_t definision? I know it needs one to prevent this error message, but is it correct for ssh to have a getty_t definision?

Jul  4 08:05:33 gatekeeper kernel: avc:  denied  { use } for  pid=339 exe=/usr/b

in/ssh path=/dev/tty3 dev=03:01 ino=71770 scontext=root:sysadm_r:sysadm_ssh_t tc ontext=system_u:system_r:getty_t tclass=fd

I am running debian (woody), with kernel from NSA, and packages from Russell's site.

Many thanks in advance,

Spencer
-----BEGIN PGP SIGNATURE-----
Version: Hush 2.1
Note: This signature can be verified at https://www.hushtools.com

wmAEARECACAFAj0kVwUZHGdkc21hcnNoYWxsQGh1c2htYWlsLmNvbQAKCRC4zrK67KP4 z0DlAJ9ACPH8CG6Pw2HI4Ld6nxULeC8sogCfeYsD+vujZTeTgiBQ5rPgneoXpOs= =KdUn
-----END PGP SIGNATURE-----

Communicate in total privacy.
Get your free encrypted email at https://www.hushmail.com/?l=2

Looking for a good deal on a domain name? http://www.hush.com/partners/offers.cgi?id=domainpeople

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

Sir,

Quoted 12 lines · --- [email protected] wrote:

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hello,

I know I have not been trying to configure SELinux for very long, but this does not look correct to me. Should ssh have a getty_t definision? I know it needs one to prevent this error message, but is it correct for ssh to have a getty_t definision?

Quoted 7 lines
Jul  4 08:05:33 gatekeeper kernel: avc:  denied  { use } for  pid=339

exe=/usr/bin/ssh path=/dev/tty3 dev=03:01 ino=71770 scontext=root:sysadm_r:sysadm_ssh_t tcontext=system_u:system_r:getty_t tclass=fd

I am running debian (woody), with kernel from NSA, and packages from Russell's site.

To me, it looks like ssh is trying to access /dev/tty3 and failing
because it isn't allowed the "use" action for the getty_t domain from its own domain. Try the following rule:

allow sysadm_ssh_t getty_t:fd use;

(Note to others: what does "use" mean?)

Quoted 4 lines

Many thanks in advance,

Spencer

Brad

=====
Brad Chapman

Permanent e-mails: [email protected]
[email protected]
[email protected]

__________________________________________________
Do You Yahoo!?
Sign up for SBC Yahoo! Dial - First Month Free
http://sbc.yahoo.com

--
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
In reply to [email protected]
Quoted 9 lines · On Thu, 4 Jul 2002 09:19, [email protected] wrote:

I know I have not been trying to configure SELinux for very long, but this does not look correct to me. Should ssh have a getty_t definision? I know it needs one to prevent this error message, but is it correct for ssh to have a getty_t definision?

Jul  4 08:05:33 gatekeeper kernel: avc:  denied  { use } for  pid=339

exe=/usr/b in/ssh path=/dev/tty3 dev=03:01 ino=71770 scontext=root:sysadm_r:sysadm_ssh_t tc ontext=system_u:system_r:getty_t tclass=fd

I've made considerable changes to fd inheriting in my recent policy (much of which is not published yet). After I merge my policy tree with the new NSA release I'll release it with a solution to this and many other issues.

In the mean time I suggest just putting the following in your policy:
allow { sysadm_ssh_t user_ssh_t } getty_t:fd use;

This allows the ssh program when run by the user or the sysadm to use the file handles of files opened by getty_t.

Quoted 2 lines

I am running debian (woody), with kernel from NSA, and packages from Russell's site.

In future please CC me about such issues, it'll get you a faster response and is more conveniant for me.

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.

#3 lore raw
In reply to [email protected]
Quoted 7 lines · On Thu, 4 Jul 2002 [email protected] wrote:

I know I have not been trying to configure SELinux for very long, but this does not look correct to me. Should ssh have a getty_t definision? I know it needs one to prevent this error message, but is it correct for ssh to have a getty_t definision?

Jul  4 08:05:33 gatekeeper kernel: avc:  denied  { use } for  pid=339 exe=/usr/b

in/ssh path=/dev/tty3 dev=03:01 ino=71770 scontext=root:sysadm_r:sysadm_ssh_t tc ontext=system_u:system_r:getty_t tclass=fd

I am running debian (woody), with kernel from NSA, and packages from Russell's site.

This indicates that the ssh client program is inheriting a descriptor originally opened by getty. This doesn't show up on our RedHat systems - we only need to grant fd use permission to the login domains (local_login_t), but it seems harmless to grant this permission.

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