All of lore.kernel.org
 help / color / mirror / Atom feed
From: Luke Kenneth Casson Leighton <lkcl@lkcl.net>
To: openssh-unix-dev@mindrot.org, pam-list@redhat.com,
	SE-Linux <selinux@tycho.nsa.gov>
Subject: issue with SE/Linux - sshd not giving access to /dev/pts/[n]
Date: Tue, 1 Jun 2004 09:03:45 +0000	[thread overview]
Message-ID: <20040601090345.GM8312@lkcl.net> (raw)

hi there,

i have an issue on my newly created Debian/SELinux/unstable system.

i have pam 0.77 se1 installed
ssh            3.8.1p1-4      (OpenSSH)
and libselinux1 1.12-1.

i can log in as root, fine.

but i cannot log in as an ordinary user, and i had to grant
special permission to the _user_ process (NOT sshd or pam
before a setuid and exec is carried out) to access
/dev/pts/0.

in other words, if i understand this correctly, there is a
bug somewhere in either sshd or pam where control of the
tty is given at the wrong point, or is not given at all.

(russell talks of relabelling the tty, i'm not sure what that
would involve.)

... except if the user is root :) :) whereupon magically
it works fiine :)

okay, so does anyone on the openssh or pam lists understand
what this might about?  does it ring any bells?

l.


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

             reply	other threads:[~2004-06-02  3:53 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-01  9:03 Luke Kenneth Casson Leighton [this message]
     [not found] ` <40BC51DD.8090609@zip.com.au>
2004-06-01 10:32   ` issue with SE/Linux - sshd not giving access to /dev/pts/[n] Luke Kenneth Casson Leighton
2004-06-02  6:31 ` Russell Coker
2004-06-02 17:23   ` Stephen Smalley
2004-06-03  4:04     ` Russell Coker
2004-06-03 12:41       ` Stephen Smalley
2004-06-03 13:14         ` Stephen Smalley
2004-06-04 11:32           ` Russell Coker
2004-06-04 12:08             ` Stephen Smalley
2004-06-09 17:21             ` Daniel J Walsh
2004-06-10  6:26               ` Russell Coker

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=20040601090345.GM8312@lkcl.net \
    --to=lkcl@lkcl.net \
    --cc=openssh-unix-dev@mindrot.org \
    --cc=pam-list@redhat.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.