All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jim McCullough <jim.mccullough@gmail.com>
To: ivg2@cornell.edu
Cc: SELinux <selinux@tycho.nsa.gov>
Subject: Re: TTY question
Date: Tue, 8 Feb 2005 22:10:37 -0500	[thread overview]
Message-ID: <ae023b6005020819101763ba8d@mail.gmail.com> (raw)
In-Reply-To: <1107915334.6602.1.camel@cobra.ivg2.net>

tty refers to the system console or virtual consoles accessable via
terminal and keyboard.  pty is the designation for any remote
connections assignments, ie.  ssh user shell.  The main purpose is to
separate console user from the remote user for accountability.   TTY's
are not able to generate the high volume load that a PTY would for
physical reasons;  unless you build a killer keyboard for it.

  By setting up different rules for tty/pty on a user.  Console access
could allow extended privileges, where in remote access from another
system would block that access.   For the rest, I will have to check
on that later; or someone else may provide assistance.  I am currently
stuck in patching windows ...... again.

Jim McCullough


On Tue, 08 Feb 2005 21:15:34 -0500, Ivan Gyurdiev <ivg2@cornell.edu> wrote:
> Hi,
> 
> I don't quite understand the difference between all the TTY/PTY devices
> on Linux - could you explain how this works a bit, so that I will know
> for the future.
> 
> Which of those rules would be required for stdin/stdout?
> 
> allow $1_$2_t tty_device_t:chr_file rw_file_perms;
> allow $1_$2_t $1_tty_device_t:chr_file rw_file_perms;
> 
> allow $1_$2_t devtty_t:chr_file rw_file_perms;
> allow $1_$2_t devpts_t:dir r_dir_perms;
> allow $1_$2_t $1_devpts_t:chr_file rw_file_perms;
> 
> What about proc permissions required?
> 
> Can some of those rules be put in a macro of some sort.
> I see tty rules all over the selinux policy, and perhaps
> they could be made more consistent with a macro.
> 
> --
> Ivan Gyurdiev <ivg2@cornell.edu>
> Cornell University
> 
> --
> 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.
> 


-- 
Jim McCullough

--
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:[~2005-02-09  3:10 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-09  2:15 TTY question Ivan Gyurdiev
2005-02-09  3:10 ` Jim McCullough [this message]
2005-02-09 13:06 ` Stephen Smalley
2005-02-10  2:02   ` Ivan Gyurdiev
2005-02-10 12:46     ` Stephen Smalley
2005-02-10 13:48       ` Ivan Gyurdiev
2005-02-10 18:04         ` Ivan Gyurdiev
2005-02-10 18:09           ` Stephen Smalley
2005-02-10 19:15           ` Ivan Gyurdiev
2005-02-10 19:31             ` Stephen Smalley
2005-02-10 20:29               ` Ivan Gyurdiev
2005-02-10 20:31                 ` Stephen Smalley
2005-02-10 21:12                   ` Ivan Gyurdiev
2005-02-10 21:16                     ` Stephen Smalley
2005-02-10 21:33                       ` Ivan Gyurdiev
2005-02-10 22:27                         ` Daniel J Walsh
2005-02-10 21:39                       ` Ivan Gyurdiev
2005-02-10 21:41                         ` Stephen Smalley
  -- strict thread matches above, loose matches on Subject: below --
2004-05-03 18:51 tty question Dvorkin

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=ae023b6005020819101763ba8d@mail.gmail.com \
    --to=jim.mccullough@gmail.com \
    --cc=ivg2@cornell.edu \
    --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.