From: Tom <tom@lemuria.org>
To: joshmccormack@travelersdiary.com
Cc: SELinux Mail List <selinux@tycho.nsa.gov>
Subject: Re: Debian Investigation Report after Server Compromises (fwd)
Date: Tue, 2 Dec 2003 20:04:42 +0100 [thread overview]
Message-ID: <20031202200441.I18433@lemuria.org> (raw)
In-Reply-To: <Pine.LNX.4.44.0312021036000.14896-100000@westhost39.westhost.net>; from joshmccormack@travelersdiary.com on Tue, Dec 02, 2003 at 10:37:40AM -0600
On Tue, Dec 02, 2003 at 10:37:40AM -0600, joshmccormack@travelersdiary.com wrote:
> Sorry this is so long, but I couldn't find it online anywhere to send a link out. I'd love some perspective on this from people using SELinux, on Debian ideally.
As I learned earlier this year, protection of the system once the
kernel has been broken open is outside the scope of SELinux.
It's an interesting topic, though. And it will certainly grow in
importance as the blackhats are concentrating more on kernel exploits
and less on userspace exploits. Which is a trend we've been seing for
at least a year now.
--
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-12-02 19:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-02 16:37 Debian Investigation Report after Server Compromises (fwd) joshmccormack
2003-12-02 19:04 ` Tom [this message]
2003-12-02 22:14 ` Colin Walters
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=20031202200441.I18433@lemuria.org \
--to=tom@lemuria.org \
--cc=joshmccormack@travelersdiary.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.