From: ascii <ascii@katamail.com>
To: gentoo-security@lists.gentoo.org
Subject: Re: [gentoo-security] mount noexec and ro
Date: Sat, 09 Dec 2006 05:21:56 +0100 [thread overview]
Message-ID: <457A39E4.5050109@katamail.com> (raw)
Message-ID: <20061209031915.506559@host216-188.pool8250.interbusiness.it> (raw)
In-Reply-To: <200612090334.31689.joe.knall@gmx.net>
Joe Knall wrote:
> When I get you right, you mean the P in Lamp makes these limitations
> (ro, noexec, nodev, chroot ...) nonsense.
only the noexec is defeated from scripts, ro nodev chrooting are
obviously safe from this
..but..
noexec on linux is futile since you could use /lib/ld-linux.so to exec
bins on a noexec mount point
if you make ld-linux.so -x then you have to rebuild all binaries
statically linked : )
..so..
it's better to get some acl/rbac system like grsec+pax and (rsbac or
selinux) to get sure things happens right
yes, it could be some time expensive to write/adapt the rules to your
current system but it worth the effort
regards,
Francesco 'ascii' Ongaro
http://www.ush.it/
--
gentoo-security@gentoo.org mailing list
prev parent reply other threads:[~2006-12-09 3:27 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-04 11:11 [gentoo-security] mount noexec and ro Joe Knall
2006-11-04 12:03 ` Wolfram Schlich
2006-11-04 12:47 ` Eduardo Tongson
2006-11-04 13:27 ` Joe Knall
2006-11-04 15:00 ` Paul de Vrieze
2006-11-04 16:27 ` Joe Knall
2006-11-04 19:03 ` Paul de Vrieze
2006-11-06 5:58 ` Miguel Angel Tormo Alfaro
2006-12-07 17:44 ` Miguel Sousa Filipe
2006-12-09 2:34 ` Joe Knall
[not found] ` <20061209031915.506559@host216-188.pool8250.interbusiness.it>
2006-12-09 4:21 ` ascii [this message]
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=457A39E4.5050109@katamail.com \
--to=ascii@katamail.com \
--cc=gentoo-security@lists.gentoo.org \
/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