On Mon, 2006-02-06 at 20:44 +0000, [EMAIL PROTECTED] wrote:
> On Mon, Feb 06, 2006 at 10:51:59AM +0800, Ow Mun Heng wrote:
> > Hi All,
> > 
> >     I do believe that this is an unsolved issue. I've search through the
> > grsec forums and according to it, There is a need to do a gradm -D (to
> > disable) gradm prior to be able to do a shutdown.  (I've not tried it as
> > I don't have access to the system now)

Okay.. I went back and tried. gradm supposedly isn't set up yet. 

#gradm -S 
GRSEC is disabled

So that's not the issue

> > 
> > 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)


> (in the subject line, put
> p or so iirc),

Again. I don't understand.
>  it can't kill the ssh process, thus hopefully giving you
> a second chance to login and set things right. (Yes, this has saved me
> in the past.)

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.

Many Thanks

-- 
Ow Mun Heng
Gentoo/Linux on DELL D600 1.4Ghz 1.5GB RAM
98% Microsoft(tm) Free!! 
Neuromancer 08:33:12 up 23:33, 3 users, load average: 0.96, 5.45, 9.78 


-- 
[email protected] mailing list

Reply via email to