From: "Zack Weinberg" <zack@codesourcery.com>
To: Matthew Galgoci <mgalgoci@redhat.com>
Cc: overseers@sources.redhat.com
Subject: Re: have we been sucked by suckit?
Date: Thu, 04 Dec 2003 10:03:00 -0000 [thread overview]
Message-ID: <873cc0yk5w.fsf@codesourcery.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0312040047210.27326-100000@lacrosse.corp.redhat.com> (Matthew Galgoci's message of "Thu, 4 Dec 2003 00:51:29 -0500 (EST)")
Matthew Galgoci <mgalgoci@redhat.com> writes:
>> The machine never runs X11, so knocking CAP_SYS_RAWIO out of the
>> capability bounding set might be a good move.
>
> I'd sooner rip out /dev/mem, /dev/kmem, and all the vm86 support.
I don't think that does anything about iopl(); but clearing
CAP_SYS_RAWIO does.
Deleting /dev/mem and /dev/kmem is a good idea, but an attacker with
root can just mknod them right back unless CAP_SYS_MKNOD is cleared.
> SELinux will let us restict things nicely. I don't think the
> draconian approach above will help terribly.
>
> I'm angling for some selinux training and I hope to make selinux on sources
> a reality in the next 6 to 8 months.
cool.
zw
next prev parent reply other threads:[~2003-12-04 10:03 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-03 23:21 Joe Buck
2003-12-04 0:09 ` law
2003-12-04 0:18 ` Joe Buck
2003-12-04 1:08 ` Christopher Faylor
2003-12-04 4:25 ` law
2003-12-04 5:44 ` Matthew Galgoci
2003-12-04 6:19 ` Christopher Faylor
2003-12-04 1:31 ` Matthew Galgoci
2003-12-04 1:49 ` Christopher Faylor
2003-12-04 2:17 ` Matthew Galgoci
2003-12-04 2:36 ` Matthew Galgoci
2003-12-04 2:50 ` Zack Weinberg
2003-12-04 2:55 ` Phil Edwards
2003-12-04 5:51 ` Matthew Galgoci
2003-12-04 10:03 ` Zack Weinberg [this message]
2003-12-04 11:12 ` Matthew Galgoci
[not found] <200312040328.hB43S2ON017317@speedy.slc.redhat.com>
2003-12-04 5:39 ` Matthew Galgoci
2003-12-04 6:32 ` Christopher Faylor
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=873cc0yk5w.fsf@codesourcery.com \
--to=zack@codesourcery.com \
--cc=mgalgoci@redhat.com \
--cc=overseers@sources.redhat.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).