Re: Serious Linux 2.0.34 security problem

From: Jim Bourne (jbourneat_private)
Date: Tue Jun 30 1998 - 12:13:15 PDT

Next message: Segv: "(no subject)"

Previous message: Here in my world I am God: "QPopper Exploit"
Maybe in reply to: David Luyer: "Serious Linux 2.0.34 security problem"
Next in thread: Theo de Raadt: "Re: Serious Linux 2.0.34 security problem"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

On Tue, 30 Jun 1998, David Luyer wrote:

> I just saw this mentioned on linux-kernel and confirmed it;

Item to note, on non-glibc systems you must add

#define O_ASYNC FASYNC

as O_ASYNC is not defined (libc 5.4.44), but is defined in glibc header file
/usr/include/fcntlbits.h.  FASYNC is defined in asm*/fcntl.h of the kernel
headers.

Regards,
Jim

> David.
>

Next message: Segv: "(no subject)"
Previous message: Here in my world I am God: "QPopper Exploit"
Maybe in reply to: David Luyer: "Serious Linux 2.0.34 security problem"
Next in thread: Theo de Raadt: "Re: Serious Linux 2.0.34 security problem"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

This archive was generated by hypermail 2b30 : Fri Apr 13 2001 - 14:01:10 PDT