public inbox for gentoo-hardened@lists.gentoo.org
 help / color / mirror / Atom feed
From: andrewg@felinemenace.org
To: gentoo-hardened@lists.gentoo.org
Subject: Re: [gentoo-hardened] Grsec and shutdown (unable to umount / )
Date: Tue, 7 Feb 2006 11:31:38 +0000	[thread overview]
Message-ID: <20060207113138.GC8265@pluto> (raw)
In-Reply-To: <1139272723.10903.5.camel@neuromancer.home.net>

> > > 
> > > I just want to verify if there is anyone here who also suffers this and
> > > what are the proper/needed steps to avoid this? (it's really painful to
> > > have to remember this and do a gradm -D each time)
> > >
> > 
> > If you have the sshd flag marked as protected 
> 
> Huh. Please elaborate. I'm new to using a hardened kernel/toolchain etc.
> (but not new to gentoo)
> 

http://grsecurity.net/gracldoc.htm

>From the sample policy file that ships with grsec,

# the d flag protects /proc fd and mem entries for sshd
# all daemons should have 'p' in their subject mode to prevent
# an attacker from killing the service (and restarting it with trojaned
# config file or taking the port it reserved to run a trojaned service)

subject /usr/sbin/sshd dpo

> 
> I get it. I didn't try to see if SSHD was still running. I'll give it
> another go when I get a chance.
>

Thanks,
Andrew Griffiths
-- 
gentoo-hardened@gentoo.org mailing list



  reply	other threads:[~2006-02-07  1:31 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-06  2:51 [gentoo-hardened] Grsec and shutdown (unable to umount / ) Ow Mun Heng
     [not found] ` <20060206204412.GB8265@pluto>
2006-02-07  0:38   ` Ow Mun Heng
2006-02-07 11:31     ` andrewg [this message]
2006-02-13  5:48       ` [gentoo-hardened] Grsec and shutdown (unable to umount / ) - Problem with Cron and PS Ow Mun Heng
2006-02-13  8:54 ` [gentoo-hardened] Grsec and shutdown (unable to umount / ) Petre Rodan

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=20060207113138.GC8265@pluto \
    --to=andrewg@felinemenace.org \
    --cc=gentoo-hardened@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