From: Daniel J Walsh <dwalsh@redhat.com>
To: ivg2@cornell.edu
Cc: Stephen Smalley <sds@tycho.nsa.gov>, selinux@tycho.nsa.gov
Subject: Re: /dev/pts/x use denials
Date: Mon, 04 Apr 2005 11:40:54 -0400 [thread overview]
Message-ID: <42516006.9030500@redhat.com> (raw)
In-Reply-To: <1112629380.29574.6.camel@cobra.ivg2.net>
Ivan Gyurdiev wrote:
>>I don't see sysadm_tmp_t anywhere above.
>>
>>
>
>Right, that was a typo.. I'm sure I meant sysadm_devpts_t
>(or at least I hope I did - sysadm_tmp_t doesn't make sense)
>
>
>
>>I do see staff_t fd's, but that
>>just shows that the descriptor was opened by a staff_t process and then
>>inherited across the su, nothing surprising there. Earlier versions of
>>pam_selinux did try closing and re-opening descriptors 0-2 as newrole
>>does, but that proved problematic. su likely just needs to be directly
>>patched rather than using pam_selinux.
>>
>>
>
>What was the problem?
>I remember another message about this, but I didn't understand it then -
>I see what you mean now.
>
>
>
Closing and reopeing a tty device in a pam module is not a good idea.
--
--
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.
prev parent reply other threads:[~2005-04-04 15:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-03 23:00 /dev/pts/x use denials Ivan Gyurdiev
2005-04-03 23:13 ` Ivan Gyurdiev
2005-04-04 15:09 ` Daniel J Walsh
2005-04-04 15:13 ` Stephen Smalley
2005-04-04 15:43 ` Ivan Gyurdiev
2005-04-04 15:39 ` Stephen Smalley
2005-04-04 15:40 ` Daniel J Walsh [this message]
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=42516006.9030500@redhat.com \
--to=dwalsh@redhat.com \
--cc=ivg2@cornell.edu \
--cc=sds@tycho.nsa.gov \
--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.