From: devzero@web.de
To: Dave Jones <davej@redhat.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: another kconfig target for building monolithic kernel (for security) ?
Date: Sat, 29 Apr 2006 19:11:31 +0200 [thread overview]
Message-ID: <1094007413@web.de> (raw)
hello !
do we need to have write access to /dev/kmem - especially on a server without X ?
iirc, write access can be disabled, for example with addons like grsecurity.
(don`t know what will be broken besides X, though)
regards
roland
> -----Ursprüngliche Nachricht-----
> Von: Dave Jones <davej@redhat.com>
> Gesendet: 29.04.06 18:43:41
> An: devzero@web.de
> CC: linux-kernel@vger.kernel.org
> Betreff: Re: another kconfig target for building monolithic kernel (for security) ?
> On Sat, Apr 29, 2006 at 03:03:55PM +0200, devzero@web.de wrote:
>
> > i want to harden a linux system (dedicated root server on the internet) by recompiling the kernel without support for lkm (to prevent installation of lkm based rootkits etc)
>
> Loading modules via /dev/kmem is trivial thanks to a bunch of tutorials and
> examples on the web, so this alone doesn't make life that much more difficult for attackers.
>
> Dave
>
> --
> http://www.codemonkey.org.uk
_______________________________________________________________
SMS schreiben mit WEB.DE FreeMail - einfach, schnell und
kostenguenstig. Jetzt gleich testen! http://f.web.de/?mc=021192
next reply other threads:[~2006-04-29 17:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-29 17:11 devzero [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-04-30 23:07 another kconfig target for building monolithic kernel (for security) ? devzero
2006-04-30 12:31 devzero
2006-04-30 13:15 ` Arjan van de Ven
2006-04-29 13:03 devzero
2006-04-29 16:43 ` Dave Jones
2006-04-29 21:22 ` Arjan van de Ven
2006-04-30 10:57 ` Nix
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=1094007413@web.de \
--to=devzero@web.de \
--cc=davej@redhat.com \
--cc=linux-kernel@vger.kernel.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