From: Tom <tom@lemuria.org>
To: Bill Laut <wlsel@verizon.net>
Cc: SELinux <SELinux@tycho.nsa.gov>
Subject: Re: X-Windows and Client-side Buffer Overruns (was Re: Updated Release)
Date: Thu, 31 Jul 2003 04:45:21 +0200 [thread overview]
Message-ID: <20030731044521.H13872@lemuria.org> (raw)
In-Reply-To: <200307301803.29302.wlsel@verizon.net>; from wlsel@verizon.net on Wed, Jul 30, 2003 at 06:03:29PM -0400
On Wed, Jul 30, 2003 at 06:03:29PM -0400, Bill Laut wrote:
> This leads me to the question: While considerable work has been done to
> protect the system from server app compromises, what about protecting the
> system from server-based buffer overrun attacks on clients running under
> SELinux?
Some work has been done in this area. Russell wrote a policy for an irc
client as an example. It should be easy to write one for a mailer along
those lines.
--
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:[~2003-07-31 2:45 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-11 19:41 Updated Release Howard Holm
2003-07-11 23:31 ` Christopher J. PeBenito
2003-07-14 11:59 ` Stephen Smalley
2003-07-30 22:03 ` X-Windows and Client-side Buffer Overruns (was Re: Updated Release) Bill Laut
2003-07-31 2:45 ` Tom [this message]
2003-07-31 15:26 ` Russell Coker
2003-07-31 15:38 ` Tom
2003-07-31 16:26 ` Bill Laut
2003-07-31 23:41 ` Russell Coker
2003-08-01 17:20 ` Bill Laut
2003-08-08 20:12 ` X-Windows and Client-side Buffer Overruns Florian Weimer
2003-08-08 20:05 ` Florian Weimer
2003-07-31 2:56 ` Updated Release Bill Laut
2003-07-31 12:20 ` 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=20030731044521.H13872@lemuria.org \
--to=tom@lemuria.org \
--cc=SELinux@tycho.nsa.gov \
--cc=wlsel@verizon.net \
/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.