[BACK]Return to errata27.html CVS log [TXT][DIR] Up to [local] / www

Annotation of www/errata27.html, Revision 1.3

1.1       deraadt     1: <!DOCTYPE HTML PUBLIC  "-//IETF//DTD HTML Strict//EN">
                      2: <html>
                      3: <head>
                      4: <title>OpenBSD 2.7 errata</title>
                      5: <link rev=made href=mailto:www@openbsd.org>
                      6: <meta name="resource-type" content="document">
                      7: <meta name="description" content="the OpenBSD CD errata page">
                      8: <meta name="keywords" content="openbsd,cd,errata">
                      9: <meta name="distribution" content="global">
                     10: <meta name="copyright" content="This document copyright 1997-1998 by OpenBSD.">
                     11: </head>
                     12:
                     13: <BODY BGCOLOR="#FFFFFF" TEXT="#000000" LINK="#23238E">
                     14:
                     15: <img alt="[OpenBSD]" height=30 width=141 SRC="images/smalltitle.gif">
                     16: <h2><font color=#0000e0>
                     17: This is the OpenBSD 2.7 release errata &amp; patch list:
                     18:
                     19: </font></h2>
                     20:
                     21: <hr>
                     22: <a href=stable.html>For OpenBSD patch branch information, please refer here.</a><br>
                     23: <a href=errata21.html>For 2.1 errata, please refer here</a>.<br>
                     24: <a href=errata22.html>For 2.2 errata, please refer here</a>.<br>
                     25: <a href=errata23.html>For 2.3 errata, please refer here</a>.<br>
                     26: <a href=errata24.html>For 2.4 errata, please refer here</a>.<br>
                     27: <a href=errata25.html>For 2.5 errata, please refer here</a>.<br>
                     28: <a href=errata26.html>For 2.6 errata, please refer here</a>.<br>
                     29: <a href=errata27.html>For 2.7 errata, please refer here</a>.<br>
                     30: <a href=errata.html>For 2.8 errata, please refer here</a>.<br>
                     31: <hr>
                     32:
                     33: <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.7.tar.gz>
                     34: You can also fetch a tar.gz file containing all the following patches</a>.
                     35: This file is updated once a day.
                     36:
                     37: <p> The patches below are available in CVS via the
                     38: <code>OPENBSD_2_7</code> <a href="stable.html">patch branch</a>.
                     39:
                     40: <p>
                     41: For more detailed information on install patches to OpenBSD, please
                     42: consult the <a href="./faq/faq10.html#10.14">OpenBSD FAQ</a>.
                     43: <hr>
                     44:
                     45: <dl>
                     46: <a name=all></a>
                     47: <li><h3><font color=#e00000>All architectures</font></h3>
                     48: <ul>
1.3     ! deraadt    49: <a name=zsconsole> </a>
        !            50: <li><font color=#009000><strong>002: IMPLEMENTATION FIX: Nov 10, 2000</strong></font><br>
        !            51: In ssh(1), skey support for SSH1 protocol was broken.  Some people might consider
        !            52: that kind of important.<br>
        !            53: <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.7/common/035_sshskey.patch>
        !            54: A source code patch exists which remedies this problem.</a>
        !            55: <p>
1.2       aaron      56: <a name=execsubr> </a>
                     57: <li><font color=#009000><strong>033: RELIABILITY FIX: Nov 6, 2000</strong></font><br>
                     58: Invalid fields in the exec header could cause a crash.<br>
                     59: <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.7/common/033_execsubr.patch>
                     60: A source code patch exists which remedies this problem.</a>
                     61: <p>
1.1       deraadt    62: <a name=xtrans> </a>
                     63: <li><font color=#009000><strong>032: SECURITY FIX: Oct 26, 2000</strong></font><br>
                     64: There are two possibly exploitable potential buffer overflows in the X11
                     65: libraries using the xtrans code. One of these vulnerabilities was
                     66: reported to the
                     67: <a href="http://www.securityfocus.com/archive/1/139436">BUGTRAQ</a>
                     68: mailing list.
                     69: <br>
                     70: <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.7/common/032_xtrans.patch>
                     71: A source code patch exists which remedies this problem.</a>
                     72: <p>
                     73: <a name=httpd></a>
                     74: <li><font color=#009000><strong>031: SECURITY FIX: Oct 18, 2000</strong></font><br>
                     75: Apache has several bugs in <tt>mod_rewrite</tt> and <tt>mod_vhost_alias</tt>
                     76: that could cause arbirtary files accessible to the www user on the server
                     77: to be exposed under certain configurations when these modules are used.
                     78: (These modules are not active by default).
                     79: <br>
                     80: <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.7/common/031_httpd.patch>
                     81: A source code patch exists which remedies this problem.</a>
                     82: <p>
                     83: <a name=telnetd></a>
                     84: <li><font color=#009000><strong>030: SECURITY FIX: Oct 10, 2000</strong></font><br>
                     85: The telnet daemon does not strip out the TERMINFO, TERMINFO_DIRS, TERMPATH
                     86: and TERMCAP (when it starts with a '/') environment variables.
                     87: <br>
                     88: <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.7/common/030_telnetd.patch>
                     89: A source code patch exists which remedies this problem.</a>
                     90: <p>
                     91: <a name=sendmail></a>
                     92: <li><font color=#009000><strong>029: RELIABILITY FIX: Oct 9, 2000</strong></font><br>
                     93: There is a non-exploitable buffer overflow in sendmail's test mode.
                     94: <br>
                     95: <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.7/common/029_sendmail.patch>
                     96: A source code patch exists which remedies this problem.</a>
                     97: <p>
                     98: <a name=format_strings></a>
                     99: <li><font color=#009000><strong>028: SECURITY FIX: Oct 6, 2000</strong></font><br>
                    100: There are printf-style format string bugs in several privileged programs.
                    101: <br>
                    102: <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.7/common/028_format_strings.patch>
                    103: A source code patch exists which remedies this problem.</a>
                    104: <p>
                    105: <a name=curses></a>
                    106: <li><font color=#009000><strong>027: SECURITY FIX: Oct 6, 2000</strong></font><br>
                    107: libcurses honored terminal descriptions in the $HOME/.terminfo directory
                    108: as well as in the TERMCAP environment variable for setuid and setgid
                    109: applications.
                    110: <br>
                    111: <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.7/common/027_curses.patch>
                    112: A source code patch exists which remedies this problem.</a>
                    113: <p>
                    114: <a name=talkd></a>
                    115: <li><font color=#009000><strong>026: SECURITY FIX: Oct 6, 2000</strong></font><br>
                    116: A format string vulnerability exists in talkd(8).  It is not clear
                    117: yet what the impact is.
                    118: <br>
                    119: <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.7/common/026_talkd.patch>
                    120: A source code patch exists which remedies this problem.</a>
                    121: <p>
                    122: <a name=pw_error></a>
                    123: <li><font color=#009000><strong>025: SECURITY FIX: Oct 3, 2000</strong></font><br>
                    124: A format string vulnerability exists in the pw_error(3) function.  This
                    125: manifests itself as a security hole in the chpass utility.  As a workaround
                    126: which disables its functionality, do
                    127: <pre>
                    128: # chmod u-s /usr/bin/chpass
                    129: </pre>
                    130: <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.7/common/025_pw_error.patch>
                    131: A source code patch exists which remedies this problem.</a>
                    132: <p>
                    133: <a name=ipsec></a>
                    134: <li><font color=#009000><strong>024: SECURITY FIX: Sep 18, 2000</strong></font><br>
                    135: Bad ESP/AH packets could cause a crash under certain conditions.
                    136: <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.7/common/024_ipsec.patch><br>
                    137: A source code patch exists which remedies this problem.</a>
                    138: <p>
                    139: <a name=xlock></a>
                    140: <li><font color=#009000><strong>023: SECURITY FIX: Aug 16, 2000</strong></font><br>
                    141: A format string vulnerability exists in xlock. As a workaround which disables
                    142: its functionality, do
                    143: <pre>
                    144: # chmod u-s /usr/X11R6/bin/xlock
                    145: </pre>
                    146: <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.7/common/023_xlock.patch>
                    147: A source code patch exists which remedies this problem.</a>
                    148: <p>
                    149: <a name=X11_libs></a>
                    150: <li><font color=#009000><strong>021: SECURITY FIX: July 14, 2000</strong></font><br>
                    151: Various problems in X11 libraries have various side effects.  We provide a
                    152: jumbo patch to fix them.<p>
                    153: <ul>
                    154:     <li><a href="http://www.securityfocus.com/templates/archive.pike?list=1&date=2000-05-15&msg=Pine.LNX.4.21.0005181947210.17658-100000@ferret.lmh.ox.ac.uk">
                    155:     Nasty X Server Dos</a><br>
                    156:     This is fixed by the patch to <b>xc/programs/Xsever/os/secauth.c</b>.
                    157:     <li><a href="http://www.securityfocus.com/templates/archive.pike?list=1&date=2000-06-15&msg=Pine.LNX.4.21.0006192251480.9945-100000@ferret.lmh.ox.ac.uk">
                    158:     Various nasty libX11 holes</a><br>
                    159:     This is covered by the patches to <b>xc/lib/X11</b>.
                    160:     <li><a href="http://www.securityfocus.com/templates/archive.pike?list=1&date=2000-06-15&msg=Pine.LNX.4.21.0006192220220.9945-100000@ferret.lmh.ox.ac.uk">
                    161:     libICE DoS</a><br>
                    162:     This is covered by the patches to <b>xc/lib/ICE</b>.
                    163:     <li><a href="http://www.securityfocus.com/templates/archive.pike?list=1&date=2000-04-15&msg=Pine.LNX.4.10.10004161835150.863-100000@localhost">
                    164:     Server overflow</a><br>
                    165:     This is covered by the patches to <b>xc/programs/Xserver/xkb</b>.
                    166:     <br>
                    167:     Note that the default OpenBSD install is not vulnerable to this, since the
                    168:     the XFree86 Xwrapper already has tests for bad arguments.
                    169: </ul>
                    170: <br>
                    171: <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.7/common/021_X11_libs.patch>
                    172: A source code patch exists which remedies these problems.</a><br>
                    173: <strong>Note 1:</strong> tcl/tk is required to build X11 from source.<br>
                    174: <strong>Note 2:</strong> When re-building use the command
                    175: `make DESTDIR=/ build' or you will get an error in the last
                    176: step of the build (makewhatis).  If you forget to set DESTDIR you can
                    177: ignore the build error.   The whatis database will be rebuilt the next
                    178: time /etc/weekly runs.
                    179: <p>
                    180: <a name=ftpd></a>
                    181: <li><font color=#009000><strong>019: SECURITY FIX: July 5, 2000</strong></font><br>
                    182: Just like pretty much all the other unix ftp daemons on the planet,
                    183: ftpd had a remote root hole in it.  Luckily, ftpd was not enabled by default.
                    184: The problem exists if anonymous ftp is enabled.
                    185: <br>
                    186: <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.7/common/019_ftpd.patch>
                    187: A source code patch exists which remedies this problem.</a>
                    188: <p>
                    189: <a name=mopd></a>
                    190: <li><font color=#009000><strong>018: SECURITY FIX: July 5, 2000</strong></font><br>
                    191: Mopd contained a buffer overflow.
                    192: <br>
                    193: <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.7/common/018_mopd.patch>
                    194: A source code patch exists which remedies this problem.</a>
                    195: <p>
                    196: <a name=screen></a>
                    197: <li><font color=#009000><strong>017: INSTALLATION FIX: July 3, 2000</strong></font>
                    198: <br>
                    199: The screen package shipped with 2.7 does not install itself properly.  The
                    200: existing package in 2.7/packages/_ARCH_/screen-3.9.5.tgz has been renamed to
                    201: screen-3.9.5.tgz.old and a replacement package has been provided under the
                    202: name screen-3.9.5p1.tgz.
                    203: <br>
                    204: <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.7/ports/017_screen.patch>
                    205: A source code patch exists which remedies this problem.</a>
                    206: <p>
                    207: <a name=libedit></a>
                    208: <li><font color=#009000><strong>013: SECURITY FIX: June 28, 2000</strong></font><br>
                    209: libedit would check for a <b>.editrc</b> file in the current directory.
                    210: That behaviour is not nice; this does not turn into a security problem in
                    211: any real world situation that we know of, but a patch is available anyways.
                    212: <br>
                    213: <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.7/common/013_libedit.patch>
                    214: A source code patch exists which remedies this problem.</a>
                    215: <p>
                    216: <a name=dhclient></a>
                    217: <li><font color=#009000><strong>012: SECURITY FIX: June 24, 2000</strong></font><br>
                    218: A serious bug in dhclient(8) could allow strings from a malicious dhcp
                    219: server to be executed in the shell as root.
                    220: <br>
                    221: <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.7/common/012_dhclient.patch>
                    222: A source code patch exists which remedies this problem.</a>
                    223: <p>
                    224: <a name=isakmpd></a>
                    225: <li><font color=#009000><strong>009: SECURITY FIX: June 9, 2000</strong></font><br>
                    226: A serious bug in isakmpd(8) policy handling wherein policy
                    227: verification could be completely bypassed in isakmpd.
                    228: <br>
                    229: <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.7/common/009_isakmpd.patch>
                    230: A source code patch exists which remedies this problem.</a>
                    231: <p>
                    232: <a name=msdosfs></a>
                    233: <li><font color=#009000><strong>008: RELIABILITY FIX: June 8, 2000</strong></font><br>
                    234: Some operations in msdosfs could result in a system panic.
                    235: <br>
                    236: <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.7/common/008_msdosfs.patch>
                    237: A source code patch exists which remedies this problem.</a>
                    238: <p>
                    239: <a name=cd9660></a>
                    240: <li><font color=#009000><strong>007: RELIABILITY FIX: June 8, 2000</strong></font><br>
                    241: NFS exporting of CD filesystems caused a system panic.
                    242: <br>
                    243: <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.7/common/007_cd9660.patch>
                    244: A source code patch exists which remedies this problem.</a>
                    245: <p>
                    246: <a name=uselogin></a>
                    247: <li><font color=#009000><strong>006: SECURITY FIX: June 6, 2000</strong></font><br>
                    248: The non-default UseLogin feature in <b>/etc/sshd_config</b> is broken and should not
                    249: be used.  On other operating systems, it results in a hole.<br>
                    250: Avoid use of this feature, or update to OpenSSH 2.1.1 or later if you must use it.
                    251: <p>
                    252: <a name=ipopts></a>
                    253: <li><font color=#009000><strong>005: RELIABILITY FIX: May 29, 2000</strong></font><br>
                    254: Parse IPv4 options more carefully.  It is not yet clear if this can even be used
                    255: to crash the machine remote or locally.
                    256: <br>
                    257: <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.7/common/005_ipopts.patch>
                    258: A source code patch exists which remedies this problem.</a>
                    259: <p>
                    260: <a name=route></a>
                    261: <li><font color=#009000><strong>004: RELIABILITY FIX: May 29, 2000</strong></font><br>
                    262: Certain routing table modifications by the superuser could cause a system panic.
                    263: <br>
                    264: <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.7/common/004_route.patch>
                    265: A source code patch exists which remedies this problem.</a>
                    266: <p>
                    267: <a name=bridge></a>
                    268: <li><font color=#009000><strong>003: SECURITY FIX: May 26, 2000</strong></font><br>
                    269: It is possible to bypass the <i>learning</i> flag on an interface if frames
                    270: go directly to the machine acting as a
                    271: <a href="http://www.openbsd.org/cgi-bin/man.cgi?query=bridge&sektion=4">bridge</a>.
                    272: <br>
                    273: <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.7/common/003_bridge.patch>
                    274: A source code patch exists which remedies this problem.</a>
                    275: <p>
                    276: <a name=ef></a>
                    277: <li><font color=#009000><strong>002: DRIVER FIX: May 26, 2000</strong></font><br>
                    278: The
                    279: <a href="http://www.openbsd.org/cgi-bin/man.cgi?query=ef&sektion=4">ef(4)</a>
                    280: driver will complain when adding an address with ifconfig
                    281: (ifconfig: SIOCAIFADDR: Invalid argument).<br>
                    282: <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.7/common/002_ef.patch>
                    283: A source code patch exists which remedies this problem.</a>
                    284: <p>
                    285: <a name=ipf></a>
                    286: <li><font color=#009000><strong>001: SECURITY FIX: May 25, 2000</strong></font><br>
                    287: A misuse of
                    288: <a href="http://www.openbsd.org/cgi-bin/man.cgi?query=ipf&sektion=8">ipf(8)</a>
                    289: <i>keep-state</i> rules can result in firewall rules being bypassed.<br>
                    290: <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.7/common/001_ipf.patch>
                    291: A source code patch exists</a>, which remedies this problem, and updates ipf
                    292: to version 3.3.16.
                    293: <p>
                    294: </ul>
                    295: <p>
                    296: <a name=i386></a>
                    297: <li><h3><font color=#e00000>i386</font></h3>
                    298: <ul>
                    299: <a name=xlhash></a>
                    300: <li><font color=#009000><strong>016: DRIVER BUG: July 2, 2000</strong></font><br>
                    301: The <a href="http://www.openbsd.org/cgi-bin/man.cgi?query=xl&sektion=4">xl(4)</a>
                    302: driver supporting various 3com cards, had a bug which prevented the multicast
                    303: filter from working correctly on the 3c905B, thus preventing many IPv6 things
                    304: from working.
                    305: <br>
                    306: <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.7/i386/016_xlhash.patch>
                    307: A source code patch exists which remedies this problem.</a>
                    308: <p>
                    309: <a name=ste></a>
                    310: <li><font color=#009000><strong>015: DRIVER BUG: June 30, 2000</strong></font><br>
                    311: The <a href="http://www.openbsd.org/cgi-bin/man.cgi?query=ste&sektion=4">ste(4)</a>
                    312: driver supporting Ethernet cards based on the Sundance ST201 chipset
                    313: (i.e., the D-Link 550TX) has a bug which causes the machine to panic at
                    314: boot-time.
                    315: <br>
                    316: <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.7/i386/015_ste.patch>
                    317: A source code patch exists which remedies this problem.</a>
                    318: <p>
                    319: <a name=pcvt></a>
                    320: <li><font color=#009000><strong>014: DRIVER BUG: June 30, 2000</strong></font><br>
                    321: The PC console driver (PCVT) has two bugs. Display problems can result if
                    322: reverse video mode is turned on or off twice in a row. This patch also
                    323: fixes a problem with scrolling region handling that has been seen by many
                    324: users trying to use the BitchX irc client with the screen program.<br>
                    325: <br>
                    326: <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.7/i386/014_pcvt.patch>
                    327: There is now a second revision of the source code patch which remedies this problem.</a>
                    328: <p>
                    329: <a name=if_an></a>
                    330: <li><font color=#009000><strong>011: DRIVER BUG: June 17, 2000</strong></font><br>
                    331: The <a href="http://www.openbsd.org/cgi-bin/man.cgi?query=an&sektion=4">an(4)</a>
                    332: Aironet Communications 4500/4800 IEEE 802.11DS driver has a bug which prevents
                    333: <a href="http://www.openbsd.org/cgi-bin/man.cgi?query=ancontrol&sektion=8">ancontrol(8)</a> from working correctly, instead causing a panic.
                    334: <br>
                    335: <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.7/i386/011_an.patch>
                    336: A source code patch exists which remedies this problem.</a>
                    337: <p>
                    338: </ul>
                    339: <p>
                    340: <a name=mac68k></a>
                    341: <li><h3><font color=#e00000>mac68k</font></h3>
                    342: <ul>
                    343: <a name=mac68k_arandom></a>
                    344: <li><font color=#009000><strong>022: INSTALLATION FIX: July 14, 2000</strong></font>
                    345: <br>
                    346: The MacOS installer shipped with OpenBSD 2.7 does not correctly make all
                    347: devices, specifically it does not make the <tt>/dev/arandom</tt> device
                    348: needed for the userland crypto such as ssh to work.  The problem shows itself
                    349: when ssh-keygen fails to make RSA or DSA keys, resulting in messages like
                    350: <b>RSA-generate_keys failed</b> or <b>DSA-generate_keys failed</b>.
                    351: <br>
                    352: To work around this, once your machine is up and running run the following
                    353: commands as root:
                    354: <tt><pre>
                    355: cd /dev
                    356: ./MAKEDEV arandom
                    357: </pre></tt>
                    358: <p>
                    359: After doing this (and possibly installing one of the ssl27 packages),
                    360: reboot your machine and it will generate ssh keys correctly.
                    361: </ul>
                    362: <p>
                    363: <a name=sparc></a>
                    364: <li><h3><font color=#e00000>sparc</font></h3>
                    365: <ul>
1.3     ! deraadt   366: <a name=zsconsole> </a>
        !           367: <li><font color=#009000><strong>033: RELIABILITY FIX: Nov 10, 2000</strong></font><br>
        !           368: When running a sparc with a serial console, certain types of interrupts would
        !           369: cause great grief.<br>
        !           370: <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.7/sparc/034_zsconsole.patch>
        !           371: A source code patch exists which remedies this problem.</a>
        !           372: <p>
1.1       deraadt   373: </ul>
                    374: <p>
                    375: <a name=amiga></a>
                    376: <li><h3><font color=#e00000>amiga</font></h3>
                    377: <ul>
                    378: <a name=amiga_cd></a>
                    379: <li><font color=#009000><strong>010: CD DISTRIBUTION ERROR: June 15, 2000</strong></font><br>
                    380: On the 2.7 CD media, the <b>amiga</b> distribution contains two pairs of archives
                    381: files for installation, ie:
                    382: <pre>
                    383: -rw-r--r--  1 root  mirftp  20191465 Apr 29 14:27 base27.tar.gz
                    384: -rw-r--r--  1 root  mirftp  20291753 May 13 19:33 base27.tgz
                    385: -rw-r--r--  1 root  mirftp  13699507 Apr 29 14:26 comp27.tar.gz
                    386: -rw-r--r--  1 root  mirftp  13748096 May 13 19:33 comp27.tgz
                    387: -rw-r--r--  1 root  mirftp   1005376 Apr 29 14:26 etc27.tar.gz
                    388: -rw-r--r--  1 root  mirftp   1010772 May 13 19:33 etc27.tgz
                    389: -rw-r--r--  1 root  mirftp   2755567 Apr 29 14:26 game27.tar.gz
                    390: -rw-r--r--  1 root  mirftp   2755624 May 13 19:33 game27.tgz
                    391: -rw-r--r--  1 root  mirftp   5002872 Apr 29 14:26 man27.tar.gz
                    392: -rw-r--r--  1 root  mirftp   5038896 May 13 19:33 man27.tgz
                    393: -rw-r--r--  1 root  mirftp   1684356 Apr 29 14:26 misc27.tar.gz
                    394: -rw-r--r--  1 root  mirftp   1684381 May 13 19:33 misc27.tgz
                    395: </pre>
                    396: The installation script will list ALL of these files.  For proper
                    397: operation one should install the <b>*.tgz</b> versions, and deselect
                    398: the <b>*.tar.gz</b> versions.<br>
                    399: The FTP area sets do not suffer from this problem.
                    400: <p>
                    401: </ul>
                    402: <p>
                    403: <a name=pmax></a>
                    404: <li><h3><font color=#e00000>pmax</font></h3>
                    405: <ul>
                    406: <a name=pmax_msgbuf></a>
                    407: <li><font color=#009000><strong>020: KERNEL BUG: July 10, 2000</strong></font><br>
                    408: As originally shipped, the pmax port would fail to install due to
                    409: <b>/kern/msgbuf</b> bugs.<br>
                    410: The neccessary fixes have been merged,
                    411: and the binaries needed re-released on the FTP site.<br>
                    412: However, the 2.7 <b>srcsys.tar.gz</b> file has not been updated.<br>
                    413: If you recompile a kernel, you should use either the
                    414: <a href=stable.html>stable release source tree</a> or apply the
                    415: provided patch to a 2.7 source tree.
                    416: <br>
                    417: <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.7/pmax/020_pmax_msgbuf.patch>
                    418: A source code patch exists which remedies this problem.</a>
                    419: <p>
                    420: </ul>
                    421: <p>
                    422: <a name=arc></a>
                    423: <li><h3><font color=#e00000>arc</font></h3>
                    424: <ul>
                    425: <li>No problems identified yet.
                    426: </ul>
                    427: <p>
                    428: <a name=alpha></a>
                    429: <li><h3><font color=#e00000>alpha</font></h3>
                    430: <ul>
                    431: <li>No problems identified yet.
                    432: </ul>
                    433: <p>
                    434: <a name=hp300></a>
                    435: <li><h3><font color=#e00000>hp300</font></h3>
                    436: <ul>
                    437: <li>No problems identified yet.
                    438: </ul>
                    439: <p>
                    440: <a name=mvme68k></a>
                    441: <li><h3><font color=#e00000>mvme68k</font></h3>
                    442: <ul>
                    443: <li>No problems identified yet.
                    444: </ul>
                    445: <p>
                    446: <a name=powerpc></a>
                    447: <li><h3><font color=#e00000>powerpc</font></h3>
                    448: <ul>
                    449: <li>No problems identified yet.
                    450: </ul>
                    451:
                    452: </dl>
                    453: <br>
                    454:
                    455: <hr>
                    456: <a href=stable.html>For OpenBSD patch branch information, please refer here.</a><br>
                    457: <a href=errata21.html>For 2.1 errata, please refer here</a>.<br>
                    458: <a href=errata22.html>For 2.2 errata, please refer here</a>.<br>
                    459: <a href=errata23.html>For 2.3 errata, please refer here</a>.<br>
                    460: <a href=errata24.html>For 2.4 errata, please refer here</a>.<br>
                    461: <a href=errata25.html>For 2.5 errata, please refer here</a>.<br>
                    462: <a href=errata26.html>For 2.6 errata, please refer here</a>.<br>
                    463: <a href=errata27.html>For 2.7 errata, please refer here</a>.<br>
                    464: <a href=errata.html>For 2.8 errata, please refer here</a>.<br>
                    465: <hr>
                    466:
                    467: <a href=index.html><img height=24 width=24 src=back.gif border=0 alt=OpenBSD></a>
                    468: <a href=mailto:www@openbsd.org>www@openbsd.org</a>
1.3     ! deraadt   469: <br><small>$OpenBSD: errata27.html,v 1.2 2000/11/06 19:12:50 aaron Exp $</small>
1.1       deraadt   470:
                    471: </body>
                    472: </html>