1 |
On Mon, 2006-02-06 at 20:44 +0000, andrewg@××××××××××××.org wrote: |
2 |
> On Mon, Feb 06, 2006 at 10:51:59AM +0800, Ow Mun Heng wrote: |
3 |
> > Hi All, |
4 |
> > |
5 |
> > I do believe that this is an unsolved issue. I've search through the |
6 |
> > grsec forums and according to it, There is a need to do a gradm -D (to |
7 |
> > disable) gradm prior to be able to do a shutdown. (I've not tried it as |
8 |
> > I don't have access to the system now) |
9 |
|
10 |
Okay.. I went back and tried. gradm supposedly isn't set up yet. |
11 |
|
12 |
#gradm -S |
13 |
GRSEC is disabled |
14 |
|
15 |
So that's not the issue |
16 |
|
17 |
> > |
18 |
> > I just want to verify if there is anyone here who also suffers this and |
19 |
> > what are the proper/needed steps to avoid this? (it's really painful to |
20 |
> > have to remember this and do a gradm -D each time) |
21 |
> > |
22 |
> |
23 |
> If you have the sshd flag marked as protected |
24 |
|
25 |
Huh. Please elaborate. I'm new to using a hardened kernel/toolchain etc. |
26 |
(but not new to gentoo) |
27 |
|
28 |
|
29 |
> (in the subject line, put |
30 |
> p or so iirc), |
31 |
|
32 |
Again. I don't understand. |
33 |
> it can't kill the ssh process, thus hopefully giving you |
34 |
> a second chance to login and set things right. (Yes, this has saved me |
35 |
> in the past.) |
36 |
|
37 |
I get it. I didn't try to see if SSHD was still running. I'll give it |
38 |
another go when I get a chance. |
39 |
|
40 |
Many Thanks |
41 |
|
42 |
-- |
43 |
Ow Mun Heng |
44 |
Gentoo/Linux on DELL D600 1.4Ghz 1.5GB RAM |
45 |
98% Microsoft(tm) Free!! |
46 |
Neuromancer 08:33:12 up 23:33, 3 users, load average: 0.96, 5.45, 9.78 |
47 |
|
48 |
|
49 |
-- |
50 |
gentoo-hardened@g.o mailing list |