Copyright © 2000, 2001, 2002, 2003, 2004 The FreeBSD Documentation Project
-$FreeBSD: src/release/doc/en_US.ISO8859-1/errata/article.sgml,v 1.66
-2004/03/05 04:19:06 bmah Exp $
+
$FreeBSD: src/release/doc/en_US.ISO8859-1/errata/article.sgml,v 1.67
+2004/03/30 17:43:26 kensmith Exp $
(30 Jan 2004, updated 28 Feb 2004) A bug in +href="http://www.FreeBSD.org/cgi/man.cgi?query=mksnap_ffs&sektion=8&manpath=FreeBSD+5.2-current"> mksnap_ffs(8) causes the creation of a filesystem snapshot to reset the flags on the filesystem to their default values. The possible consequences depend on local usage, but can include disabling extended access control lists or enabling the use of setuid executables stored on an untrusted filesystem. This bug also affects the +href="http://www.FreeBSD.org/cgi/man.cgi?query=dump&sektion=8&manpath=FreeBSD+5.2-current"> dump(8) -L option, which uses +href="http://www.FreeBSD.org/cgi/man.cgi?query=mksnap_ffs&sektion=8&manpath=FreeBSD+5.2-current"> mksnap_ffs(8). Note that +href="http://www.FreeBSD.org/cgi/man.cgi?query=mksnap_ffs&sektion=8&manpath=FreeBSD+5.2-current"> mksnap_ffs(8) is normally only available to the superuser and members of the operator group. This bug has been fixed on the FreeBSD 5.2-RELEASE @@ -115,7 +115,7 @@ target="_top">FreeBSD-SA-04:01.
(8 Feb 2004, updated 28 Feb 2004) A bug with the System V Shared Memory interface (specifically the +href="http://www.FreeBSD.org/cgi/man.cgi?query=shmat&sektion=2&manpath=FreeBSD+5.2-current"> shmat(2) system call) can cause a shared memory segment to reference unallocated kernel memory. In turn, this can permit a local attacker to gain unauthorized access to parts of kernel memory, @@ -128,7 +128,7 @@ target="_top">FreeBSD-SA-04:02.
(28 Feb 2004) It is possible, under some circumstances, for a processor with superuser privileges inside a +href="http://www.FreeBSD.org/cgi/man.cgi?query=jail&sektion=8&manpath=FreeBSD+5.2-current"> jail(8) environment to change its root directory to a different jail, giving it read and write access to the files and directories within. This vulnerability has been closed on the @@ -146,21 +146,22 @@ href="ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/advisories/FreeBSD-SA-04:04.tcp.asc target="_top">FreeBSD-SA-04:04 contains more details, as well as information on patching existing systems.
-(17 Mar 2004) By performing a specially crafted SSL/TLS handshake with -an application that uses OpenSSL a null pointer may be dereferenced. This -may in turn cause the application to crash, resulting in a denial of service -attack. For more information see the Security Advisory -FreeBSD-SA-04:05 which contains more details and instructions -on how to patch existing systems.
+(17 Mar 2004) By performing a specially crafted SSL/TLS handshake with an application +that uses OpenSSL a null pointer may be dereferenced. This may in turn cause the +application to crash, resulting in a denial of service attack. For more information see +the Security Advisory FreeBSD-SA-04:05 which contains more details and instructions on how to +patch existing systems.
(29 Mar 2004) A local attacker may take advantage of a programming error in the -handling of certain IPv6 socket options in the - -setsockopt(2) system call -to read portions of kernel memory without proper authorization. This may result in disclosure of -sensitive data, or potentially cause a panic. See Security Advisory - +setsockopt(2) +system call to read portions of kernel memory without proper authorization. This may +result in disclosure of sensitive data, or potentially cause a panic. See Security +Advisory FreeBSD-SA-04:06 for a more detailed description and instructions on how to patch existing systems.
(9 Jan 2004) Due to a change in +href="http://www.FreeBSD.org/cgi/man.cgi?query=cpp&sektion=1&manpath=FreeBSD+5.2-current"> cpp(1) behavior, the login screen for -xdm(1) is in -black and white, even on systems with color displays. As a workaround, update to a newer -version of the xdm(1) is in black and +white, even on systems with color displays. As a workaround, update to a newer version of +the x11/XFree86-4-clients port/package.
@@ -187,9 +188,9 @@ class="VARNAME">hint.acpi.0.disabled kernel environment variable. These pr are being investigated. For problems that have not already been reported (check the mailing list archives before posting), sending the output of +href="http://www.FreeBSD.org/cgi/man.cgi?query=dmesg&sektion=8&manpath=FreeBSD+5.2-current"> dmesg(8) and +href="http://www.FreeBSD.org/cgi/man.cgi?query=acpidump&sektion=8&manpath=FreeBSD+5.2-current"> acpidump(8) to the FreeBSD-CURRENT mailing list may help diagnose the problem. @@ -218,26 +219,26 @@ the hint.acpi.0.disabled kernel environment variable.Some of these problems were addressed in FreeBSD 5.2.1-RELEASE with the import of a newer +href="http://www.FreeBSD.org/cgi/man.cgi?query=ata&sektion=4&manpath=FreeBSD+5.2-current"> ata(4) from 5.2-CURRENT.
(9 Jan 2004) Installing over NFS when using the install floppies requires that the nfsclient.ko module be manually loaded from the third floppy disk. This can be done by following the prompts when +href="http://www.FreeBSD.org/cgi/man.cgi?query=sysinstall&sektion=8&manpath=FreeBSD+5.2-current"> sysinstall(8) launches to load a driver off of the third floppy disk.
(9 Jan 2004) The use of multiple vchans (virtual audio channels with dynamic mixing in software) in the +href="http://www.FreeBSD.org/cgi/man.cgi?query=pcm&sektion=4&manpath=FreeBSD+5.2-current"> pcm(4) driver has been known to cause some instability.
(10 Jan 2004) Although APIC interrupt routing seems to work correctly on many systems, on some others (such as some laptops) it can cause various errors, such as +href="http://www.FreeBSD.org/cgi/man.cgi?query=ata&sektion=4&manpath=FreeBSD+5.2-current"> ata(4) errors or hangs when starting or exiting X11. For these situations, it may be advisable to disable APIC routing, using the ``safe mode'' of the bootloader or the