! RELIABILITY FIXAll architectures
A local user can crash the system by reading a file larger than 64meg
from an ext2fs partition.
--- 85,91 ----
! RELIABILITY FIXAll architectures
A local user can crash the system by reading a file larger than 64meg
from an ext2fs partition.
***************
*** 95,115 ****
A source code patch exists which remedies this problem.
! SECURITY FIXAll architectures
A race condition existed between accept(2) and select(2) which could
permit an attacker to hang sockets from remote.
--- 131,137 ----
and the tcp decoding patch.
! SECURITY FIXAll architectures
A race condition existed between accept(2) and select(2) which could
permit an attacker to hang sockets from remote.
***************
*** 141,169 ****
A source code patch exists which remedies this problem.
! FUNCTIONALITY FIXAll architectures
The readv(2) and writev(2) system calls would not accept a struct iovec
! with an iov_len of 0. This causes a db test in perl to fail.
A source code patch exists which remedies this problem.
! FUNCTIONALITY FIXAll architectures
During bootup, kvm_mkdb may exit with the error "kvm_mkdb: cannot allocate
memory".
--- 139,167 ----
A source code patch exists which remedies this problem.
! FUNCTIONALITY FIXAll architectures
The readv(2) and writev(2) system calls would not accept a struct iovec
! with an iov_len of 0. This causes a db test in perl to fail.
A source code patch exists which remedies this problem.
! FUNCTIONALITY FIXAll architectures
During bootup, kvm_mkdb may exit with the error "kvm_mkdb: cannot allocate
memory".
***************
*** 171,177 ****
A source code patch exists which remedies this problem.
! FUNCTIONALITY FIXAll architectures
A problem with writing to NFS version 3 mounted filesystems from Solaris 7
hosts exists. Attempts to create files will result in an error such as
--- 169,175 ----
A source code patch exists which remedies this problem.
! FUNCTIONALITY FIXAll architectures
A problem with writing to NFS version 3 mounted filesystems from Solaris 7
hosts exists. Attempts to create files will result in an error such as
***************
*** 180,186 ****
A source code patch exists which remedies this problem.
! FUNCTIONALITY FIXAll architectures
A problem with NFS version 3 mounts on big endian machines (m68k, sparc
and powerpc) exists when mounting filesystems larger than 2gig. You
--- 178,184 ----
A source code patch exists which remedies this problem.
! FUNCTIONALITY FIXAll architectures
A problem with NFS version 3 mounts on big endian machines (m68k, sparc
and powerpc) exists when mounting filesystems larger than 2gig. You
***************
*** 190,196 ****
A source code patch exists which remedies this problem.
! SECURITY FIXAll architectures
A security problem exists in the curses and ocurses libraries that affect
setuid programs linked with -lcurses or -locurses.
--- 188,194 ----
A source code patch exists which remedies this problem.
! SECURITY FIXAll architectures
A security problem exists in the curses and ocurses libraries that affect
setuid programs linked with -lcurses or -locurses.
***************
*** 202,216 ****
platform. Unpack it in /usr/lib.
! FUNCTIONALITY FIXAll architectures
! A workaround for an xterm problem that causes vi to not
restore the correct cursor position on exit.
A source code patch exists which remedies this problem.
Alternately, you can also download a pre-compiled terminfo file to be
! installed as /usr/share/misc/terminfo.db. For i386,
alpha and mips, use the
little endian version. For sparc, m68k and powerpc, use the
--- 200,214 ----
platform. Unpack it in /usr/lib.
! FUNCTIONALITY FIXAll architectures
! A workaround for an xterm problem that causes vi to not
restore the correct cursor position on exit.
A source code patch exists which remedies this problem.
Alternately, you can also download a pre-compiled terminfo file to be
! installed as /usr/share/misc/terminfo.db. For i386,
alpha and mips, use the
little endian version. For sparc, m68k and powerpc, use the
***************
*** 218,231 ****
big endian version.
! SECURITY FIXAll architectures
A remotely exploitable problem exists in bootpd(8). bootpd is disabled
by default, but some people may actually be using it.
--- 216,229 ----
big endian version.
! SECURITY FIXAll architectures
A remotely exploitable problem exists in bootpd(8). bootpd is disabled
by default, but some people may actually be using it.
***************
*** 234,257 ****
This is the second version of the patch.
! FUNCTIONALITY FIX
The kernel was using a fixed and hard-coded location for the arguments
! vector passed from the /boot loader. This prevented
! /boot from placing the boot arguments vector at any
other location, causing a kernel crash early in the autoconfiguration
stage. In 2.5, the bootblocks will be modified to use a new location.
Hence, if you wish old kernels to boot on a new bootblock, those
--- 232,255 ----
This is the second version of the patch.
! FUNCTIONALITY FIX
The kernel was using a fixed and hard-coded location for the arguments
! vector passed from the /boot loader. This prevented
! /boot from placing the boot arguments vector at any
other location, causing a kernel crash early in the autoconfiguration
stage. In 2.5, the bootblocks will be modified to use a new location.
Hence, if you wish old kernels to boot on a new bootblock, those
***************
*** 260,273 ****
A source code patch exists which remedies this problem.