From: "Serge E. Hallyn" <serue@us.ibm.com>
To: "Christopher J. PeBenito" <cpebenito@tresys.com>
Cc: SELinux <selinux@tycho.nsa.gov>
Subject: Re: sereference: screen policy
Date: Mon, 16 Jan 2006 12:44:39 -0600 [thread overview]
Message-ID: <20060116184439.GC15246@sergelap.austin.ibm.com> (raw)
In-Reply-To: <1137427147.29815.232.camel@sgc>
Quoting Christopher J. PeBenito (cpebenito@tresys.com):
> The rule for the user's own terminal should be in. I don't know if we
> should trust screen to use all terminals.
>
> > allow $1_screen_t tty_device_t:lnk_file read;
>
> Looks like a mislabeled symlink. Currently the symlinks in /dev are all
> device_t, as far as I know. Looking at terminal.fc, everything is
> marked -c (with the exception of /dev/pts directory which is -d), so I'm
> not sure how this would happen.
>
> > Note that I also still need my other patch for local logins from Jan 11.
>
> Ok, I'll go back and look at it. The response you made to your email
> made me think it wasn't actually needed.
Ah, ok, I added a line to terminal.fc in my login patch to label my
/dev/ttyS1 as tty_device_t:
+/dev/.*tty[^/]* -l gen_context(system_u:object_r:tty_device _t,s0)
Let me see if removing that lets me still log in, and if so I guess I
may not need
> > allow $1_screen_t tty_device_t:lnk_file read;
in the screen template.
thanks,
-serge
--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.
next prev parent reply other threads:[~2006-01-16 18:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-12 21:48 sereference: screen policy Serge E. Hallyn
2006-01-13 16:12 ` Christopher J. PeBenito
2006-01-13 16:30 ` Serge E. Hallyn
2006-01-13 22:22 ` Serge E. Hallyn
2006-01-16 15:59 ` Christopher J. PeBenito
2006-01-16 18:44 ` Serge E. Hallyn [this message]
2006-01-16 19:48 ` Serge E. Hallyn
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20060116184439.GC15246@sergelap.austin.ibm.com \
--to=serue@us.ibm.com \
--cc=cpebenito@tresys.com \
--cc=selinux@tycho.nsa.gov \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.