article.xml revision 125606
176082Sbmah<!-- 276082Sbmah FreeBSD errata document. Unlike some of the other RELNOTESng 376082Sbmah files, this file should remain as a single SGML file, so that 476082Sbmah the dollar FreeBSD dollar header has a meaningful modification 576082Sbmah time. This file is all but useless without a datestamp on it, 676082Sbmah so we'll take some extra care to make sure it has one. 776082Sbmah 876082Sbmah (If we didn't do this, then the file with the datestamp might 976082Sbmah not be the one that received the last change in the document.) 1076082Sbmah 1176082Sbmah--> 1276082Sbmah 1376082Sbmah<!DOCTYPE article PUBLIC "-//FreeBSD//DTD DocBook V4.1-Based Extension//EN" [ 1476082Sbmah<!ENTITY % man PUBLIC "-//FreeBSD//ENTITIES DocBook Manual Page Entities//EN"> 1576082Sbmah%man; 1676082Sbmah<!ENTITY % authors PUBLIC "-//FreeBSD//ENTITIES DocBook Author Entities//EN"> 1776082Sbmah%authors; 1876082Sbmah<!ENTITY % mlists PUBLIC "-//FreeBSD//ENTITIES DocBook Mailing List Entities//EN"> 1976082Sbmah%mlists; 20119884Ssimon<!ENTITY % trademarks PUBLIC "-//FreeBSD//ENTITIES DocBook Trademark Entities//EN"> 21119884Ssimon%trademarks; 2276082Sbmah<!ENTITY % release PUBLIC "-//FreeBSD//ENTITIES Release Specification//EN"> 2376082Sbmah%release; 24124312Sbmah<!ENTITY % misc PUBLIC "-//FreeBSD//ENTITIES DocBook Miscellaneous FreeBSD Entities//EN"> 25124312Sbmah%misc; 2676082Sbmah]> 2776082Sbmah 2876082Sbmah<article> 2976082Sbmah <articleinfo> 30109307Sbmah <title>&os; 31109543Sbmah<![ %release.type.snapshot [ 32109543Sbmah &release.prev; 33109543Sbmah]]> 34109543Sbmah<![ %release.type.release [ 35109543Sbmah &release.current; 36109543Sbmah]]> 37109307Sbmah Errata</title> 3877914Sbmah 3976082Sbmah <corpauthor> 4076082Sbmah The &os; Project 4176082Sbmah </corpauthor> 4276082Sbmah 4376082Sbmah <pubdate>$FreeBSD: head/release/doc/en_US.ISO8859-1/errata/article.sgml 125606 2004-02-08 22:16:29Z bmah $</pubdate> 4476082Sbmah 4576082Sbmah <copyright> 4676082Sbmah <year>2000</year> 4776082Sbmah <year>2001</year> 4888820Sbmah <year>2002</year> 49108829Sbmah <year>2003</year> 50124312Sbmah <year>2004</year> 5176082Sbmah <holder role="mailto:doc@FreeBSD.org">The FreeBSD Documentation Project</holder> 5276082Sbmah </copyright> 53119884Ssimon 54119884Ssimon <legalnotice id="trademarks" role="trademarks"> 55119884Ssimon &tm-attrib.freebsd; 56119884Ssimon &tm-attrib.intel; 57119884Ssimon &tm-attrib.sparc; 58119884Ssimon &tm-attrib.general; 59119884Ssimon </legalnotice> 6076082Sbmah </articleinfo> 6176082Sbmah 6277914Sbmah <abstract> 6379807Sbmah <para>This document lists errata items for &os; 64109543Sbmah<![ %release.type.snapshot [ 65109543Sbmah &release.prev;, 66109543Sbmah]]> 67109543Sbmah<![ %release.type.release [ 68109543Sbmah &release.current;, 69109543Sbmah]]> 70112874Sbmah containing significant information discovered after the release 71112874Sbmah or too late in the release cycle to be otherwise included in the 72112874Sbmah release documentation. 7392295Sbmah This information includes security advisories, as well as news 7492295Sbmah relating to the software or documentation that could affect its 7592295Sbmah operation or usability. An up-to-date version of this document 7692295Sbmah should always be consulted before installing this version of 7792295Sbmah &os;.</para> 7877914Sbmah 79109307Sbmah <para>This errata document for &os; 80109543Sbmah<![ %release.type.snapshot [ 81109543Sbmah &release.prev; 82109543Sbmah]]> 83109543Sbmah<![ %release.type.release [ 84109543Sbmah &release.current; 85109543Sbmah]]> 86116130Sbmah will be maintained until the release of &os; &release.next;.</para> 8777914Sbmah </abstract> 8877914Sbmah 89109143Sroam <sect1 id="intro"> 9076082Sbmah <title>Introduction</title> 9176082Sbmah 9279807Sbmah <para>This errata document contains <quote>late-breaking news</quote> 9392295Sbmah about &os; 94109543Sbmah<![ %release.type.snapshot [ 95109543Sbmah &release.prev;. 96109543Sbmah]]> 97109543Sbmah<![ %release.type.release [ 98109543Sbmah &release.current;. 99109543Sbmah]]> 10092295Sbmah Before installing this version, it is important to consult this 10192295Sbmah document to learn about any post-release discoveries or problems 10292295Sbmah that may already have been found and fixed.</para> 10379807Sbmah 10492295Sbmah <para>Any version of this errata document actually distributed 10592295Sbmah with the release (for example, on a CDROM distribution) will be 10692295Sbmah out of date by definition, but other copies are kept updated on 10792295Sbmah the Internet and should be consulted as the <quote>current 10892295Sbmah errata</quote> for this release. These other copies of the 10992295Sbmah errata are located at <ulink 11092295Sbmah url="http://www.FreeBSD.org/releases/"></ulink>, plus any sites 11192295Sbmah which keep up-to-date mirrors of this location.</para> 11276082Sbmah 11379807Sbmah <para>Source and binary snapshots of &os; &release.branch; also 11492295Sbmah contain up-to-date copies of this document (as of the time of 11592295Sbmah the snapshot).</para> 11676082Sbmah 11777914Sbmah <para>For a list of all &os; CERT security advisories, see <ulink 11892295Sbmah url="http://www.FreeBSD.org/security/"></ulink> or <ulink 11992295Sbmah url="ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/"></ulink>.</para> 12092295Sbmah 12176082Sbmah </sect1> 12276082Sbmah 123109143Sroam <sect1 id="security"> 12476082Sbmah <title>Security Advisories</title> 125109309Sbmah 126115963Sbmah<![ %release.type.release [ 127115963Sbmah <para>No advisories.</para> 128115963Sbmah]]> 129109309Sbmah 130115963Sbmah<![ %release.type.snapshot [ 131125249Sbmah 132125249Sbmah <para>(30 Jan 2004) A bug in &man.mksnap.ffs.8; causes the creation of a 133125249Sbmah filesystem snapshot to reset the flags on the filesystem to 134125249Sbmah their default values. The possible consequences depend on local 135125249Sbmah usage, but can include disabling extended access control lists 136125249Sbmah or enabling the use of setuid executables stored on an untrusted 137125249Sbmah filesystem. This bug also affects the &man.dump.8; 138125249Sbmah <option>-L</option> option, which uses &man.mksnap.ffs.8;. Note 139125249Sbmah that &man.mksnap.ffs.8; is normally only available to the 140125249Sbmah superuser and members of the <groupname>operator</groupname> 141125249Sbmah group. This bug has been fixed on the &os; &release.current; 142125249Sbmah security fix branch. For more information, see security advisory <ulink 143125249Sbmah url="ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/advisories/FreeBSD-SA-04:01.mksnap_ffs.asc">FreeBSD-SA-04:01</ulink>.</para> 144125249Sbmah 145125606Sbmah <para>(8 Feb 2004) A bug with the System V Shared Memory interface 146125606Sbmah (specifically the &man.shmat.2; system call) 147125606Sbmah can cause a shared memory segment to reference 148125606Sbmah unallocated kernel memory. In turn, this can permit a local 149125606Sbmah attacker to gain unauthorized access to parts of kernel memory, 150125606Sbmah possibly resulting in disclosure of sensitive information, 151125606Sbmah bypass of access control mechanisms, or privilege escalation. 152125606Sbmah More details, including bugfix and workaround information, 153125606Sbmah can be found in security advisory <ulink 154125606Sbmah url="ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/advisories/FreeBSD-SA-04:02.shmat.asc">FreeBSD-SA-04:02</ulink>.</para> 155125606Sbmah 156115963Sbmah]]> 157111435Sbmah 158115963Sbmah </sect1> 159111435Sbmah 160115963Sbmah <sect1 id="open-issues"> 161115963Sbmah <title>Open Issues</title> 162111834Sbmah 163115963Sbmah<![ %release.type.release [ 164115963Sbmah <para>No open issues.</para> 165115963Sbmah]]> 166112435Sbmah 167115963Sbmah<![ %release.type.snapshot [ 168124312Sbmah 169124312Sbmah <para>(9 Jan 2004) Due to a change in &man.cpp.1; behavior, the 170124312Sbmah login screen for &man.xdm.1; is in black and white, even on 171124312Sbmah systems with color displays. As a workaround, update to a newer 172124312Sbmah version of the 173124312Sbmah <filename role="package">x11/XFree86-4-clients</filename> 174124312Sbmah port/package.</para> 175124312Sbmah 176124312Sbmah <para>(9 Jan 2004) There remain some residual problems with ACPI. 177124312Sbmah In some cases, systems may behave erratically, or hang at boot 178124312Sbmah time. As a workaround, disable ACPI, using the <quote>safe 179124312Sbmah mode</quote> option of the bootloader or using the 180124312Sbmah <varname>hint.acpi.0.disabled</varname> kernel environment 181124312Sbmah variable. These problems are being investigated. For problems 182124312Sbmah that have not already been reported (check the mailing list 183124312Sbmah archives <emphasis>before</emphasis> posting), sending the 184124312Sbmah output of &man.dmesg.8; and &man.acpidump.8; to the 185124312Sbmah &a.current; may help diagnose the problem.</para> 186124312Sbmah 187124312Sbmah <para>(9 Jan 2004) In some cases, ATA devices may behave 188124312Sbmah erratically, particularly SATA devices. Reported symptoms 189124352Sbmah include command timeouts or missing interrupts. These problems 190124312Sbmah appear to be timing-dependent, making them rather difficult to 191124312Sbmah isolate. Workarounds include:</para> 192124312Sbmah 193124312Sbmah <itemizedlist> 194124312Sbmah <listitem> 195124312Sbmah <para>Turn off ATA DMA using the <quote>safe mode</quote> 196124312Sbmah option of the bootloader or the 197124312Sbmah <varname>hw.ata.ata_dma</varname> sysctl variable.</para> 198124312Sbmah </listitem> 199124312Sbmah 200124312Sbmah <listitem> 201124312Sbmah <para>Use the host's BIOS setup options to put the ATA 202124312Sbmah controller in its <quote>legacy mode</quote>, if 203124312Sbmah available.</para> 204124312Sbmah </listitem> 205124312Sbmah 206124312Sbmah <listitem> 207124312Sbmah <para>Disable ACPI, for example using the <quote>safe mode</quote> 208124312Sbmah option of the bootloader or using the 209124312Sbmah <varname>hint.acpi.0.disabled</varname> kernel environment 210124312Sbmah variable.</para> 211124312Sbmah </listitem> 212124312Sbmah </itemizedlist> 213124312Sbmah 214124312Sbmah <para>(9 Jan 2004) Installing over NFS when using the install 215124312Sbmah floppies requires that the <filename>nfsclient.ko</filename> 216124312Sbmah module be manually loaded from the third floppy disk. This can 217124312Sbmah be done by following the prompts when &man.sysinstall.8; 218124312Sbmah launches to load a driver off of the third floppy disk.</para> 219124312Sbmah 220124312Sbmah <para>(9 Jan 2004) The use of multiple vchans (virtual audio 221124312Sbmah channels with dynamic mixing in software) in the &man.pcm.4; 222124312Sbmah driver has been known to cause some instability.</para> 223124312Sbmah 224124352Sbmah <para>(10 Jan 2004) Although APIC interrupt routing seems to work 225124352Sbmah correctly on many systems, on some others (such as some laptops) 226124352Sbmah it can cause various errors, such as &man.ata.4; errors or hangs 227124352Sbmah when starting or exiting X11. For these situations, it may be 228124352Sbmah advisable to disable APIC routing, using the <quote>safe 229124352Sbmah mode</quote> of the bootloader or the 230124352Sbmah <varname>hint.apic.0.disabled</varname> loader tunable. Note 231124352Sbmah that disabling APIC is not compatible with SMP systems.</para> 232124352Sbmah 233124352Sbmah <para>(10 Jan 2004) The NFSv4 client may panic when attempting an 234124352Sbmah NFSv4 operation against an NFSv3/NFSv2-only server. This 235124352Sbmah problem has been fixed with revision 1.4 of 236124352Sbmah <filename>src/sys/rpc/rpcclnt.c</filename> in &os; 237124352Sbmah &release.current;.</para> 238124352Sbmah 239124484Sbmah <para>(11 Jan 2004) Some problems have been encountered when using 240124484Sbmah third-party NSS modules, such as <filename>nss_ldap</filename>, 241124484Sbmah and groups with large membership lists. These have been fixed 242124484Sbmah with revision 1.2 of <filename>src/include/nss.h</filename> and 243124484Sbmah revision 1.2 of 244124484Sbmah <filename>src/lib/libc/net/nss_compat.c</filename> in &os; 245124484Sbmah &release.current;.</para> 246124484Sbmah 247124484Sbmah <para>(13 Jan 2004) The &os; &release.current; release notes 248124484Sbmah incorrectly stated that <application>GCC</application> was a 249124484Sbmah post-release GCC 3.3.3 snapshot. They should have stated that 250124484Sbmah GCC was a <emphasis>pre-release</emphasis> GCC 3.3.3 251124484Sbmah snapshot.</para> 252124484Sbmah 253124485Sbmah <para>(13 Jan 2004) The <filename 254124485Sbmah role="package">sysutils/kdeadmin3</filename> port/package has a 255124485Sbmah bug in the <application>KUser</application> component that can 256124485Sbmah cause deletion of the <username>root</username> user from the 257124485Sbmah system password file. Users are strongly urged to upgrade to 258124485Sbmah version 3.1.4_1 of this port/package.</para> 259124485Sbmah 260124801Sbmah <para>(21 Jan 2004) Some bugs in the IPsec implementation imported 261124801Sbmah from the KAME Project can result in memory objects being freed 262124801Sbmah before all references to them were removed. Reported symptoms 263124801Sbmah include erratic behavior or kernel panics after flushing the 264124801Sbmah Security Policy Database (SPD). Some of these problems have 265124801Sbmah been fixed in &os; &release.current; in rev. 1.31 of 266124801Sbmah <filename>src/sys/netinet6/ipsec.c</filename>, rev. 1.136 of 267124801Sbmah <filename>src/sys/netinet/in_pcb.c</filename>, and revs. 1.63 268124801Sbmah and 1.64 of <filename>src/sys/netkey/key.c</filename>. More 269124801Sbmah information about these problems has been posted to the 270124801Sbmah &a.current;, in particular the thread entitled <ulink 271124947Sbmah url="http://lists.FreeBSD.org/pipermail/freebsd-current/2004-January/thread.html#18084"> 272124801Sbmah <quote>[PATCH] IPSec fixes</quote></ulink>.</para> 273124801Sbmah 274115963Sbmah]]> 275112477Sbmah 27676082Sbmah </sect1> 27776082Sbmah 278109309Sbmah <sect1 id="late-news"> 279109309Sbmah <title>Late-Breaking News</title> 280109309Sbmah 281115963Sbmah<![ %release.type.release [ 282115963Sbmah <para>No news.</para> 283115963Sbmah]]> 284109583Schris 285115963Sbmah<![ %release.type.snapshot [ 286124352Sbmah 287124352Sbmah <para>(10 Jan 2004) The TCP implementation in &os; now includes 288124352Sbmah protection against a certain class of TCP MSS resource 289124352Sbmah exhaustion attacks, in the form of limits on the size and rate 290124352Sbmah of TCP segments. The first limit sets the minimum allowed 291124352Sbmah maximum TCP segment size, and is controlled by the 292124352Sbmah <varname>net.inet.tcp.minmss</varname> sysctl variable (the 293124352Sbmah default value is <literal>216</literal> bytes). The second 294124352Sbmah limit is set by the 295124352Sbmah <varname>net.inet.tcp.minmssoverload</varname> variable, and 296124352Sbmah controls the maximum rate of connections whose average segment 297124352Sbmah size is less than <varname>net.inet.tcp.minmss</varname>. 298124352Sbmah Connections exceeding this packet rate are reset and dropped. 299124352Sbmah Because this feature was added late in the &release.prev; 300124352Sbmah release cycle, connection rate limiting is disabled by default, 301124352Sbmah but can be enabled manually by assigning a non-zero value to 302124352Sbmah <varname>net.inet.tcp.minmssoverload</varname> (the default 303124352Sbmah value in &release.current; at the time of this writing is 304124352Sbmah <literal>1000</literal> packets per second).</para> 305124352Sbmah 306115963Sbmah]]> 307109309Sbmah 308115963Sbmah </sect1> 309109583Schris 31076082Sbmah</article> 311