From: Tom <tom@lemuria.org>
To: selinux@tycho.nsa.gov
Cc: Russell Coker <russell@coker.com.au>
Subject: Re: expect
Date: Mon, 2 Dec 2002 18:34:21 +0100 [thread overview]
Message-ID: <20021202183420.A16247@lemuria.org> (raw)
In-Reply-To: <200212021558.27661.russell@coker.com.au>; from russell@coker.com.au on Mon, Dec 02, 2002 at 03:58:27PM +0100
On Mon, Dec 02, 2002 at 03:58:27PM +0100, Russell Coker wrote:
> Allowing daemons the tty access could probably be addressed in another way.
> If we had a separate role and domain for starting daemons that could be
> entered with newrole (which then removes the need for run_init as the role
> would not have permission to do anything other than restarting daemons) we
> could then allow all daemons read/write/ioctl access to the terminal for it.
> Then if we deny the daemons read access to /dev (wherever possible) and
> /dev/pts (always) then after you exit the shell that newrole ran (relabelling
> your tty) the daemon won't be able to access your tty or open other ttys.
I like this idea a lot. It would make a real-life admin job much, much
easier. It's not just that sometimes you have several daemons to
(re)start, it is during development that you easily restart a given
service a couple dozen times. I know I considered the password request
a nuisance after the 5th or so time.
> I believe that this isn't as good as my solution with expect, and it isn't
> something that can be done in a hurry either.
Actually, it may turn out to be a better solution, mostly because
expect is no longer required (and a couple of the recent postings here have
shown just why that may be a good thing).
--
PGP/GPG key: http://web.lemuria.org/pubkey.html
pub 1024D/2D7A04F5 2002-05-16 Tom Vogt <tom@lemuria.org>
Key fingerprint = C731 64D1 4BCF 4C20 48A4 29B2 BF01 9FA1 2D7A 04F5
--
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:[~2002-12-02 17:34 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-29 20:02 expect Stephen D. Smalley
2002-12-01 12:08 ` expect Russell Coker
2002-12-02 14:09 ` expect Jesse Pollard
2002-12-02 14:58 ` expect Russell Coker
2002-12-02 17:34 ` Tom [this message]
2002-12-02 19:40 ` expect Russell Coker
2002-12-02 22:00 ` expect Tom
2002-12-03 11:46 ` expect Russell Coker
-- strict thread matches above, loose matches on Subject: below --
2002-11-29 15:43 expect Russell Coker
2002-10-27 19:44 expect Russell Coker
2002-10-26 20:52 expect Russell Coker
2002-10-26 21:32 ` expect Chris Albert
2002-10-26 22:07 ` expect Russell Coker
[not found] ` <3DBB2043.2010709@sympatico.ca>
2002-10-26 23:26 ` expect Russell Coker
1999-03-12 12:15 Expect Dean Takemori
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=20021202183420.A16247@lemuria.org \
--to=tom@lemuria.org \
--cc=russell@coker.com.au \
--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.