From: Hatto von Hatzfeld (hattosalesianer.de)
Date: Mon Mar 31 2003 - 15:11:19 CST

• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

On Mon, Mar 31, 2003 at 10:30:22PM +0200, Tobias Cremer wrote:
> Am Montag, 31. März 2003 10:35 schrieb Habichtsberg, R.:
> > Hi,
> > After the security update of the linux kernel,
> > in my case from k_deflt-2.4.18-57 to k_deflt-2.4.18-261,
> > I have two frozen systems.
>
> I had a frozen system after the security kernel patch twice this evening.
[...]
> It really looks like SuSE have to be more careful with building the
> patches. Of course I know that this is a question of time, but I
> rather take the workaround and wait longer for a patch than to apply a
> patch which freezes my system.

I have had a frozen system twice after installing the new kernel in a
SuSE 7.3 system (upgrading thus from 2.4.10 to 2.4.18). This never had
happened before. But I am glad that this until now did not happen to my
webserver (same SuSE 7.3, same patch). (And as I have written in another
mail in this list, my Adaptec AVA-1505AE (SCSI controller) does not work
any more.)

What is the best thing to do now - to go back to the unpatched kernel
(and to live with the security problem), to remain with the risk of a
freeze or to try the k_deflt-2.4.19-patch?

By,
Hatto

--
Check the headers for your unsubscription address
For additional commands, e-mail: suse-security-helpsuse.com
Security-related bug reports go to securitysuse.de, not here

• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]