Bugtraq mailing list archives
Re: Serious Linux 2.0.34 security problem
From: jbourne () HARDROCK ORG (Jim Bourne)
Date: Tue, 30 Jun 1998 12:13:15 -0700
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.
Current thread:
- Re: Vulnerability in 4.4BSD Secure Levels Implementation, (continued)
- Re: Vulnerability in 4.4BSD Secure Levels Implementation Darren Reed (Jun 13)
- Re: Vulnerability in 4.4BSD Secure Levels Implementation tqbf () pobox com (Jun 11)
- Re: Vulnerability in 4.4BSD Secure Levels Implementation Niall Smart (Jun 13)
- Re: Vulnerability in 4.4BSD Secure Levels Implementation Tim Newsham (Jun 26)
- check-ps 1.2 alpha 4 released Duncan Simpson (Jun 26)
- Re: Vulnerability in 4.4BSD Secure Levels Implementation tqbf () pobox com (Jun 14)
- Re: Vulnerability in 4.4BSD Secure Levels Implementation Niall Smart (Jun 28)
- Re: Vulnerability in 4.4BSD Secure Levels Implementation Tim Newsham (Jun 28)
- Re: Vulnerability in 4.4BSD Secure Levels Implementation Roger Harrison ? (Jun 29)
- Serious Linux 2.0.34 security problem David Luyer (Jun 30)
- Re: Serious Linux 2.0.34 security problem Jim Bourne (Jun 30)
- QPOPPER - FreBSD, BSDI/OS remote exploit MiG (Jun 30)