All of lore.kernel.org
 help / color / mirror / Atom feed
From: Debian User <rogelio@evoworks.evoserve.com>
To: Stephen Smalley <sds@tislabs.com>
Cc: selinux@tycho.nsa.gov
Subject: Re: sshd_devpts_t
Date: Tue, 09 Jul 2002 21:00:12 +0800	[thread overview]
Message-ID: <3D2ADE5C.4000102@evoworks.evoserve.com> (raw)
In-Reply-To: Pine.GSO.4.33.0207090849460.27193-100000@raven

Stephen Smalley wrote:

>On Tue, 9 Jul 2002, Debian User wrote:
>
>  
>
>>Has this been fixed yet? I cant ssh into my pc anymore. Where should
>>this be fixed?
>>    
>>
>
>I'm not sure what you are asking.  If you are using devfs, you will likely
>need some additional allow rules for access to devpts_t, since the
>per-domain pty labeling that we support for the devpts filesystem is not
>implemented for the devfs filesystem.  If people want more complete devfs
>support, the best way to get it would be to contribute some patches.
>  
>
I added allow rules for devpts but i prefer adding complete devfs 
support. Im not familiar with devfs but I guess there is no other way 
but to dig in and try to fix it.

>--
>Stephen D. Smalley, NAI Labs
>ssmalley@nai.com
>
>
>  
>




--
You have received this message because you are subscribed to the selinux 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:[~2002-07-09 13:00 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-09 11:34 sshd_devpts_t Debian User
2002-07-09 12:54 ` sshd_devpts_t Stephen Smalley
2002-07-09 13:00   ` Debian User [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=3D2ADE5C.4000102@evoworks.evoserve.com \
    --to=rogelio@evoworks.evoserve.com \
    --cc=sds@tislabs.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.