hi,
I use Grsecurity with High level for over 2 years now on 2.4.X without
any problems running debian woody. These daemons works fine:
ssh
postfix
courier-imap (with and without ssl)
courier-pop (with and without ssl)
apache
apache-ssl
mysql
snort
and a view other ...
The best way would be for y
On Monday 07 February 2005 at 16:17, Andras Got wrote:
> Hi,
>
> That's it, the chpax. I tried these things almost a year ago with JSP
> thingy. I googled and the like, but chpax didn't help.
>
> I meant that I selected high settings, then selected custom, then did some
> changes. :)
>
> A.
>
Hi,
That's it, the chpax. I tried these things almost a year ago with JSP thingy. I googled and the
like, but chpax didn't help.
I meant that I selected high settings, then selected custom, then did some
changes. :)
A.
Thomas Sjögren írta:
On Mon, Feb 07, 2005 at 02:10:07PM +0100, Andras Got wro
On Mon, Feb 07, 2005 at 02:10:07PM +0100, Andras Got wrote:
> You should start with grsec low and proc restricions set customly.
> Hardening your kernel is always a option.
Running grsec isn't a problem, I use on both clients and servers.
Dont start with grsec low but with the custom option,
CON
Greetings,..
Am Montag, 7. Februar 2005 14:10 schrieb Andras Got:
> Hi,
>
> You should start with grsec low and proc restricions set customly.
> Hardening your kernel is always a option. The grsec default high settings,
> and PaX break Jetty (java server container) in two, so it simply won't
> sta
Hi,
You should start with grsec low and proc restricions set customly. Hardening your kernel is always a
option. The grsec default high settings, and PaX break Jetty (java server container) in two, so it
simply won't start, gradm won't help as I know. After the grsec default low settings you shou
6 matches
Mail list logo
