From: Michael C Thompson <thompsmc@us.ibm.com>
To: Klaus Weidner <klaus@atsec.com>
Cc: Russell Coker <russell@coker.com.au>,
selinux@tycho.nsa.gov, redhat-lspp@redhat.com
Subject: Re: MLS enforcing PTYs, sshd, and newrole
Date: Thu, 12 Oct 2006 10:16:54 -0500 [thread overview]
Message-ID: <452E5C66.1060201@us.ibm.com> (raw)
In-Reply-To: <20061012144819.GF28520@w-m-p.com>
Klaus Weidner wrote:
> Of course, people deploying a system that's based on the LSPP
> configuration can choose to deviate from the evaluated configuration
> based on their own risk assessment. This could include restoring general
> access to "newrole" if they don't consider the PTY exploit to be a
> concern.
And if you want polyinstation, then an suid newrole needs to be available :)
--
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:[~2006-10-12 15:17 UTC|newest]
Thread overview: 61+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-12 7:33 MLS enforcing PTYs, sshd, and newrole Klaus Weidner
2006-10-12 10:25 ` Russell Coker
2006-10-12 14:48 ` Klaus Weidner
2006-10-12 15:16 ` Michael C Thompson [this message]
2006-10-12 16:54 ` [redhat-lspp] " Casey Schaufler
2006-10-12 15:37 ` Casey Schaufler
2006-10-19 13:21 ` [redhat-lspp] " Daniel J Walsh
2006-10-19 13:30 ` Stephen Smalley
2006-10-19 14:06 ` Daniel J Walsh
2006-10-19 14:32 ` Stephen Smalley
2006-10-21 4:37 ` Casey Schaufler
2006-10-23 16:14 ` James Antill
2006-10-23 16:39 ` Casey Schaufler
2006-10-23 16:45 ` Paul Moore
2006-10-23 18:41 ` Casey Schaufler
2006-10-24 20:37 ` James Antill
2006-10-25 0:19 ` George C. Wilson
2006-10-25 11:48 ` Stephen Smalley
2006-10-25 12:22 ` Stephen Smalley
2006-10-25 13:50 ` James Antill
2006-10-25 13:59 ` Stephen Smalley
2006-10-25 19:15 ` James Antill
2006-10-25 19:24 ` Stephen Smalley
[not found] ` <1161970810.29689.88.camel@code.and.org>
[not found] ` <1161974293.1306.167.camel@moss-spartans.epoch.ncsc.mil>
2006-10-30 20:03 ` [PATCH 1/3] " James Antill
2006-10-30 20:16 ` [PATCH 2/3] " James Antill
2006-10-30 20:22 ` [PATCH 3/3] " James Antill
2006-10-31 14:23 ` [PATCH 2/3] " Stephen Smalley
2006-10-31 14:24 ` Stephen Smalley
2006-10-31 15:00 ` James Antill
2006-10-31 15:11 ` Stephen Smalley
2006-10-31 16:04 ` James Antill
2006-10-31 16:21 ` Stephen Smalley
2006-10-31 18:33 ` James Antill
2006-11-01 12:36 ` Stephen Smalley
2007-01-04 21:34 ` [redhat-lspp] " Daniel J Walsh
2007-01-04 21:57 ` Linda Knippers
2007-01-04 22:19 ` Daniel J Walsh
2007-01-04 23:19 ` Linda Knippers
2007-01-05 1:07 ` Klaus Weidner
2007-01-05 3:05 ` Joshua Brindle
2007-01-05 3:33 ` Klaus Weidner
2007-01-05 3:35 ` Joshua Brindle
2007-01-05 4:01 ` Klaus Weidner
2007-01-05 15:56 ` Stephen Smalley
2007-01-05 16:23 ` Daniel J Walsh
2007-01-05 16:24 ` Daniel J Walsh
2007-01-05 17:05 ` Daniel J Walsh
2007-01-05 18:34 ` Stephen Smalley
2007-01-05 18:43 ` Stephen Smalley
2007-01-05 15:55 ` Stephen Smalley
2007-01-04 22:13 ` Casey Schaufler
2007-01-04 22:20 ` Daniel J Walsh
2006-10-31 14:20 ` [PATCH 1/3] " Stephen Smalley
2006-10-25 21:36 ` [redhat-lspp] " Stephen Smalley
2006-10-26 14:09 ` Daniel J Walsh
2006-10-19 13:32 ` Steve Grubb
2006-10-19 13:39 ` Stephen Smalley
2006-10-20 7:00 ` Russell Coker
2006-10-27 15:36 ` Valdis.Kletnieks
2006-10-27 23:04 ` Russell Coker
2006-10-31 14:29 ` Stephen Smalley
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=452E5C66.1060201@us.ibm.com \
--to=thompsmc@us.ibm.com \
--cc=klaus@atsec.com \
--cc=redhat-lspp@redhat.com \
--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.