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

Annotation of www/errata22.html, Revision 1.65

1.37      naddy       1: <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
1.1       deraadt     2: <html>
                      3: <head>
1.19      deraadt     4: <title>OpenBSD 2.2 errata</title>
1.37      naddy       5: <link rev=made href="mailto:www@openbsd.org">
1.1       deraadt     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">
1.27      jufi       10: <meta name="copyright" content="This document copyright 1997-2001 by OpenBSD.">
1.41      henning    11: <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
1.1       deraadt    12: </head>
                     13:
1.42      david      14: <body bgcolor="#ffffff" text="#000000" link="#23238E">
1.1       deraadt    15:
1.32      jsyn       16: <a href="index.html"><img alt="[OpenBSD]" height="30" width="141" src="images/smalltitle.gif" border="0"></a>
1.37      naddy      17: <h2><font color="#0000e0">
1.14      espie      18: This is the OpenBSD 2.2 release errata &amp; patch list:
1.1       deraadt    19: </font></h2>
                     20:
1.2       deraadt    21: <hr>
1.20      jason      22: <a href=stable.html>For OpenBSD patch branch information, please refer here.</a><br>
1.34      deraadt    23: <br>
1.35      deraadt    24: For errata on a certain release, click below:<br>
1.34      deraadt    25: <a href="errata21.html">2.1</a>,
                     26: <a href="errata23.html">2.3</a>,
                     27: <a href="errata24.html">2.4</a>,
                     28: <a href="errata25.html">2.5</a>,
                     29: <a href="errata26.html">2.6</a>,
                     30: <a href="errata27.html">2.7</a>,
                     31: <a href="errata28.html">2.8</a>,
                     32: <a href="errata29.html">2.9</a>,
                     33: <a href="errata30.html">3.0</a>,
                     34: <a href="errata31.html">3.1</a>,
1.38      deraadt    35: <a href="errata32.html">3.2</a>,
1.40      david      36: <a href="errata33.html">3.3</a>,
1.44      david      37: <a href="errata34.html">3.4</a>,
1.45      miod       38: <a href="errata35.html">3.5</a>,
1.46      deraadt    39: <a href="errata36.html">3.6</a>,
1.54      deraadt    40: <br>
1.47      deraadt    41: <a href="errata37.html">3.7</a>,
1.48      deraadt    42: <a href="errata38.html">3.8</a>,
1.49      deraadt    43: <a href="errata39.html">3.9</a>,
1.50      deraadt    44: <a href="errata40.html">4.0</a>,
1.52      merdely    45: <a href="errata41.html">4.1</a>,
1.53      deraadt    46: <a href="errata42.html">4.2</a>,
1.54      deraadt    47: <a href="errata43.html">4.3</a>,
1.56      deraadt    48: <a href="errata44.html">4.4</a>,
1.57      deraadt    49: <a href="errata45.html">4.5</a>,
1.58      deraadt    50: <a href="errata46.html">4.6</a>,
1.60      deraadt    51: <a href="errata47.html">4.7</a>,
1.61      miod       52: <a href="errata48.html">4.8</a>,
1.62      nick       53: <a href="errata49.html">4.9</a>,
1.63      sthen      54: <a href="errata50.html">5.0</a>,
1.64      deraadt    55: <a href="errata51.html">5.1</a>,
1.65    ! deraadt    56: <a href="errata52.html">5.2</a>,
        !            57: <a href="errata53.html">5.3</a>.
1.34      deraadt    58: <br>
1.2       deraadt    59: <hr>
                     60:
1.59      sthen      61: <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/2.2.tar.gz">
1.11      deraadt    62: You can also fetch a tar.gz file containing all the following patches</a>.
                     63: This file is updated once a day.
                     64:
1.21      ericj      65: <p>
1.36      deraadt    66: For more detailed information on how to install patches to OpenBSD, please
1.21      ericj      67: consult the <a href="./faq/faq10.html#10.14">OpenBSD FAQ</a>.
                     68:
1.11      deraadt    69: <hr>
                     70:
1.41      henning    71: <a name="all"></a>
                     72: <h3><font color="#e00000">All architectures</font></h3>
1.1       deraadt    73: <ul>
1.41      henning    74: <li><a name="ipsec"></a>
                     75: <font color="#009000"><strong>SECURITY FIX</strong></font><br>
1.7       deraadt    76: If IPSEC communication is attempted by starting photurisd(8) (which is
1.8       deraadt    77: disabled by default), a system crash may be evoked from remote if
                     78: an attacker uses some classes of invalid packets.
1.59      sthen      79: <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/2.2/common/ipsec.patch">
1.7       deraadt    80: A source code patch exists which remedies this problem.</a>
1.9       deraadt    81: <p>
1.41      henning    82: <li><a name="xterm-xaw"></a>
                     83: <font color="#009000"><strong>SECURITY FIX</strong></font><br>
1.5       matthieu   84: As stated in CERT advisory VB-98.04, there are buffer
1.8       deraadt    85: overrun problems in <strong>xterm</strong> related to the input-Method,
                     86: preeditType, and *Keymap resources. Additional buffer overruns exist in
                     87: the <strong>Xaw</strong> library related to the inputMethod and
                     88: preeditType resources.   The xterm(1) problem represents a security
                     89: vulnerability for any platform where xterm is installed setuid-root
                     90: (as is the case for all OpenBSD platforms).  The Xaw problem represents
                     91: a security vulnerability for any setuid-root program that uses the Xaw
                     92: library (including xterm).  Patch1 from XFree86 3.3.2 corrects
                     93: these problems.
1.59      sthen      94: <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/2.2/common/xterm-xaw.patch">
1.6       deraadt    95: We provide a version of this patch file specifically for the OpenBSD 2.2 tree</a>.
1.5       matthieu   96: <p>
1.41      henning    97: <li><a name="rmjob"></a>
                     98: <font color="#009000"><strong>SECURITY FIX</strong></font><br>
1.1       deraadt    99: An exploitable buffer mismanagement exists in a subroutine used by
                    100: lprm and lpd.  The problem is exploitable by users on a particular
                    101: machine if there is an entry in <strong>/etc/printcap</strong> which
                    102: points at a remote printer.
1.59      sthen     103: <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/2.2/common/rmjob.patch">
1.1       deraadt   104: A patch is available which corrects this behaviour</a>.
                    105: <p>
1.41      henning   106: <li><a name="uucpd"></a>
                    107: <font color="#009000"><strong>SECURITY FIX</strong></font><br>
1.1       deraadt   108: A DNS-based vulnerability exists when uucpd is used.  By default uucpd
                    109: is not enabled in the OpenBSD releases, but some sites may have enabled it.
1.59      sthen     110: <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/2.2/common/uucpd.patch">
1.1       deraadt   111: A patch is available which corrects this behaviour</a>.
                    112: <p>
1.41      henning   113: <li><a name="named"></a>
                    114: <font color="#009000"><strong>SECURITY FIX</strong></font><br>
1.1       deraadt   115: A vulnerability exists when (and only when) /etc/named.conf has the
                    116: <strong>fake-iquery</strong> option enabled.
1.59      sthen     117: <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/2.2/common/named.patch">
1.1       deraadt   118: A patch is available which corrects this behaviour</a>.
                    119: <p>
1.41      henning   120: <li><a name="ping"></a>
                    121: <font color="#009000"><strong>SECURITY FIX</strong></font><br>
1.1       deraadt   122: A vulnerability exists in ping(8); if the -R option is used to record
                    123: routes, an attacker can spoof a reply packet that will overflow inside
                    124: ping.  Preliminary investigation makes it look the worst attack
                    125: possible is to make ping crash, but one never knows...
1.59      sthen     126: <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/2.2/common/ping.patch">
1.1       deraadt   127: A patch is available which corrects this behaviour</a>.
                    128: <p>
1.41      henning   129: <li><a name="sourceroute"></a>
                    130: <strong><font color="#009000">SECURITY FIX</font></strong><br>
1.1       deraadt   131: If the sysctl variable <strong>net.inet.ip.forwarding</strong> is
                    132: enabled (value 1), but the variable <strong>net.inet.ip.sourceroute</strong>
                    133: is disabled (value 0), the kernel will block source routed packets from
                    134: going through, but will still accept source routing packets destined for
                    135: itself.  Our fix changes the <strong>net.inet.ip.sourceroute</strong>
                    136: variable semantics to mean that all source routed packets should
                    137: be blocked completely.
1.59      sthen     138: <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/2.2/common/sourceroute.patch">
1.1       deraadt   139: A kernel patch is provided</a>.
                    140: <p>
1.41      henning   141: <li><a name="ruserok"></a>
                    142: <font color="#009000"><strong>SECURITY FIX</strong></font><br>
1.1       deraadt   143: A combination localhost+remote host security problem exists if a
1.26      jsyn      144: local user running a setuid binary causes a non-existent root .rhosts
1.1       deraadt   145: file to be created via a symbolic link with a specific kind of corefile,
                    146: and then subsequently uses rsh/rlogin to enter the machine from remote.
                    147: A similar exploit might also be possible using sshd which lacks any code
                    148: for checking for deviations from the expected format in the .rhosts or
                    149: .shosts files, but we have not confirmed this yet.  The following two
                    150: fixes are recommended:
                    151: <p>
                    152: <ul>
                    153: <li>
1.59      sthen     154: <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/2.2/common/nosuidcoredump.patch">
1.1       deraadt   155: (1) A kernel patch which adds a new sysctl option which permits the
                    156: administrator to decide whether setuid corefiles should be written or not</a>.
                    157: <p>
1.59      sthen     158: <li><a href="http://ftp.openbsd.org/pub/OpenBSD/patches/2.2/common/rcmd.patch">
1.1       deraadt   159: (2) Replaces the libc ruserok() function with a more paranoid
                    160: version which detects bogus looking .rhosts files better.</a>
                    161: </ul>
                    162: <p>
                    163: If the
                    164: first patch is used to stop setuid coredumps, then the second patch is
                    165: not as important.
                    166: This problem is fixed much better in OpenBSD-current, where the kernel's
                    167: symbolic link handling has been improved such that coredumping will not
                    168: create a file on the other side of a symbolic link.  Such a patch is not
                    169: possible for the 4.4lite1 VFS layer in the OpenBSD 2.2 kernel.<p>
                    170: The problem with the ruserok() function appears to also exist in
                    171: ssh 1.2.21 and previous (the ssh people have been alerted).
                    172: <p>
1.41      henning   173: <li><a name="mmap"></a>
                    174: <strong><font color="#009000">SECURITY FIX</font></strong><br>
1.1       deraadt   175: A bug in the vm system permits a file descriptor opened read-only on a
                    176: device, to later on be mmap(2)'d read-write, and then modified.  This
                    177: does not result in a security hole by itself, but it does violate the
                    178: safety semantics which securelevels are supposed to provide.  If a user
                    179: manages to gain kmem group permissions, using this problem they can then
                    180: gain root trivially and/or turn securelevels off.
1.59      sthen     181: <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/2.2/common/vm_mmap.patch">
1.1       deraadt   182: A kernel patch is available which corrects this behaviour (this is
                    183: revision 3 of this patch)</a>.
                    184: <p>
1.37      naddy     185: <li><font color="#009000"><strong>BUILD PROCESS FIX</strong></font><br>
1.1       deraadt   186: Building an object tree from a read-only source tree (such as off a CDROM)
                    187: may fail under certain circumstances (e.g. when creating a symlink on sparc
                    188: whose target name is exactly 33 characters).  As a workaround you have to
                    189: either provide the source tree read/write, or install a newer version of
                    190: /usr/bin/readlink.
1.59      sthen     191: <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/2.2/common/readlink.c">
1.1       deraadt   192: A replacement source file exists</a>.
                    193: <p>
1.41      henning   194: <li><a name="mountd"></a>
                    195: <font color="#009000"><strong>SECURITY FIX</strong></font><br>
1.1       deraadt   196: If a line in /etc/exports which contains hostnames results in an empty
                    197: list because none of the supplied hostnames is known, mountd(8) will
                    198: accidentally export the filesystem to the world.
1.59      sthen     199: <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/2.2/common/mountd.patch">
1.1       deraadt   200: A patch is available which corrects this behaviour</a>.
                    201: <p>
1.37      naddy     202: <li><font color="#009000"><strong>RELIABILITY FIX</strong></font><br>
1.1       deraadt   203: Setting the MSG_EOR flag on a tcp packet in the send(2) family of
                    204: system calls could cause a kernel panic.
1.59      sthen     205: <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/2.2/common/send.patch">
1.1       deraadt   206: A patch</a> to return EINVAL in this case is available.
                    207: <p>
                    208: </ul>
1.41      henning   209: <a name="i386"></a>
                    210: <h3><font color="#e00000">i386</font></h3>
1.1       deraadt   211: <ul>
1.41      henning   212: <li><a name="f00f"></a>
                    213: <font color="#009000"><strong>RELIABILITY FIX</strong></font><br>
1.26      jsyn      214: The Intel P5 F00F bug was discovered after the CDRs had already been
1.1       deraadt   215: sent to the manufacturer.  This problem permits any user who has an account
                    216: to lock your machine up using a 4-line program.  The problem only affects
                    217: Intel P5 processors (the i386, i486, P-Pro, and P-II are not vulnerable,
                    218: nor are processors by other manufacturers).
1.59      sthen     219: <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/2.2/i386/f00f.patch">
1.1       deraadt   220: A kernel source-code patch is available</a>.
                    221: <p>
1.37      naddy     222: <li><font color="#009000"><strong>FUNCTIONALITY FIX</strong></font><br>
1.1       deraadt   223: Some Linux binaries will execute in SVR4 emulation mode, which is
1.12      aaron     224: definitely a problem for people who need Linux emulation to work correctly.
1.1       deraadt   225: To solve this mis-identification problem,
1.59      sthen     226: <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/2.2/i386/compat_linux.patch">
1.1       deraadt   227: a patch file is provided</a>.
                    228: <p>
1.37      naddy     229: <li><font color="#009000"><strong>RELIABILITY FIX</strong></font><br>
1.1       deraadt   230: APM can crash on machines without it.
1.59      sthen     231: <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/2.2/i386/apm.patch">
1.1       deraadt   232: A kernel source-code patch is available</a>.
                    233: <p>
1.37      naddy     234: <li><font color="#009000"><strong>INSTALLATION PROCESS FLAW</strong></font><br>
1.25      pvalchev  235: A few people are running into this problem, particularly if they had some
1.1       deraadt   236: other *BSD operating system on their machine before trying OpenBSD: if after
                    237: installation onto an IDE-based machine, the kernel fails to mount the root
                    238: partition because it thinks that it should be opening sd0 (0x400), this means
                    239: you have incorrectly setup your disklabel for the IDE drive -- the disklabel
                    240: is indicating that the drive is SCSI.
                    241: To repair this, use the floppy to run "disklabel -E wd0", then using the
                    242: "edit" command ensure the type field is set to "ST506".
                    243: <p>
                    244: </ul>
1.41      henning   245: <a name="mac68k"></a>
                    246: <h3><font color="#e00000">mac68k</font></h3>
1.1       deraadt   247: <ul>
1.37      naddy     248: <li><font color="#009000"><strong>NEW SOFTWARE</strong></font><br>
1.1       deraadt   249: Unfortunately, X11 binaries for the mac68k did not manage to make it onto the
                    250: CDROM.  However, X11 for the mac68k is immediately available from
1.59      sthen     251: <a href="http://ftp.openbsd.org/pub/OpenBSD/2.2/mac68k/X11/X11R6.tar.gz">
                    252: http://ftp.OpenBSD.org/pub/OpenBSD/2.2/mac68k/X11/X11R6.tar.gz</a>.  Please
                    253: be sure to read the <a href="http://ftp.openbsd.org/pub/OpenBSD/2.2/mac68k/X11/README.X11">README file</a> also in that directory for instructions on installing
1.1       deraadt   254: and setting up X.
                    255: <p>
1.37      naddy     256: <li><font color="#009000"><strong>INSTALLATION PROCESS FLAW</strong></font><br>
1.1       deraadt   257: As shipped on the CDROM, both the
1.59      sthen     258: <a href="http://ftp.openbsd.org/pub/OpenBSD/2.2/mac68k/bsd-generic.tar.gz">
1.1       deraadt   259: generic kernel</a>
                    260: and the
1.59      sthen     261: <a href="http://ftp.openbsd.org/pub/OpenBSD/2.2/bsd-genericbsc.tar.gz">
1.1       deraadt   262: genericsbc kernel</a>
                    263: extract themselves into the wrong place in the filesystem.
                    264: Both <strong>should</strong> extract a kernel named <tt>/bsd</tt>, but they extract
                    265: the kernel into <tt>/usr/src/sys/arch/mac68k/compile</tt> instead.
                    266: <p>
                    267: This has been fixed on the ftp release of <a href=22.html>OpenBSD 2.2</a>, and
1.59      sthen     268: fresh kernels are available from <a href="http://ftp.openbsd.org/pub/OpenBSD/2.2/mac68k">
                    269: http://ftp.OpenBSD.ORG/pub/OpenBSD/2.2/mac68k/</a>.  If at all possible,
1.1       deraadt   270: installing these kernels is recommended.
                    271: <p>
                    272: A number of possible workarounds exist if you don't have easy access to ftp
                    273: the updated kernels.  The simplest of these is to use a
                    274: MacOS program to uncompress and untar the kernel aad use the Installer's
                    275: mini-shell to "cpin" the kernel.  Alternately, you could install the kernel
                    276: with the Installer and use the mini-shell to move the binary from <tt>/usr/src/...</tt> to <tt>/bsd</tt>.
                    277: <p>
                    278: </ul>
1.41      henning   279: <a name="sparc"></a>
                    280: <h3><font color="#e00000">sparc</font></h3>
1.1       deraadt   281: <ul>
1.37      naddy     282: <li><font color="#009000"><strong>RELIABILITY FIX</strong></font><br>
1.25      pvalchev  283: Older 4/xxx systems (particularly the 4/300's) cannot boot
1.1       deraadt   284: with the 2.2 kernel due to bugs in the scsi device driver.
1.59      sthen     285: <a href="http://ftp.OpenBSD.org/pub/OpenBSD/patches/2.2/sparc/esp.patch">
1.1       deraadt   286: A kernel source patch is available</a>.
                    287: Replacement kernels are available for:
1.59      sthen     288: <a href="http://ftp.OpenBSD.org/pub/OpenBSD/patches/2.2/sparc/bsd">bsd</a>,
                    289: <a href="http://ftp.OpenBSD.org/pub/OpenBSD/patches/2.2/sparc/bsd.scsi3">bsd.scsi3</a>,
1.1       deraadt   290: and a replacement for bsd.rd is coming soon.
                    291: <p>
1.41      henning   292: <li><a name="sparciommu"></a>
                    293: <font color="#009000"><strong>RELIABILITY FIX</strong></font><br>
1.1       deraadt   294: SPARCstation 4 and 5 (Microsparc 2) users may see kernel panics when
                    295: using a custom kernel configured for option sun4m only.
1.59      sthen     296: <a href="http://ftp.OpenBSD.org/pub/OpenBSD/patches/2.2/sparc/sun4m.patch">
1.1       deraadt   297: A workaround (kernel source patch) is available</a>.  Apply the patch and
                    298: then re-build your kernel.
                    299: <p>
                    300: </ul>
1.41      henning   301: <h3><font color="#e00000">amiga</font></h3>
1.1       deraadt   302: <p>
                    303: <ul>
1.37      naddy     304: <li><font color="#009000"><strong>FUNCTIONALITY FIX</strong></font><br>
1.1       deraadt   305: Missing Xamiga manual pages.  Get
1.59      sthen     306: <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/2.2/amiga/Xamiga-manual.tgz">
1.1       deraadt   307: this package</a> and execute, <i>as root</i>:<br>
                    308: <strong><b># </b>pkg_add Xamiga-manual.tgz</strong><br>
                    309: The MD5 checksum of this package is:<br>
                    310: <b>MD5 (Xamiga-manual.tgz) = 2362a7857264b9d17f65cca258b42031</b><p>
1.37      naddy     311: <li><font color="#009000"><strong>FUNCTIONALITY FIX</strong></font><br>
1.1       deraadt   312: The Ariadne ethernet support was broken, there will be both binary and
                    313: source level fixes available shortly.  If you are in a hurry mail
1.37      naddy     314: <a href="mailto:niklas@openbsd.org">Niklas</a> for a test kernel.<p>
1.1       deraadt   315: </ul>
1.41      henning   316: <a name="pmax"></a>
                    317: <h3><font color="#e00000">pmax</font></h3>
1.1       deraadt   318: <ul>
1.37      naddy     319: <li><font color="#009000"><strong>FUNCTIONALITY FIX</strong></font><br>
1.1       deraadt   320: There is a Year-1998 problem in the time-setting code (which causes the
                    321: date and time to be set incorrectly after a reboot in 1998).
1.59      sthen     322: <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/2.2/pmax/clock.patch">
1.1       deraadt   323: A source code patch file is available</a> plus replacement installation
                    324: kernels for the 2.2 release at
1.59      sthen     325: <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/2.2/pmax/bsd.NFS">bsd.NFS</a>,
                    326: <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/2.2/pmax/bsd">bsd</a>,
                    327: <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/2.2/pmax/bsd.rz0">bsd.rz0</a>.
1.1       deraadt   328: <p>
1.37      naddy     329: <li><font color="#009000"><strong>FUNCTIONALITY FIX</strong></font><br>
1.1       deraadt   330: X11 support for the 3min and 3maxplus machines was broken
                    331: due to a kernel bug.
1.59      sthen     332: <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/2.2/pmax/fb.patch">
1.1       deraadt   333: A source code patch is available</a>.
                    334: <p>
1.41      henning   335: <li><a name="ldso"></a>
                    336: <font color="#009000"><strong>SECURITY FIX</strong></font><br>
1.1       deraadt   337: A security problem in the shared library linker <strong>ld.so</strong>
                    338: requires that you replace it with a new binary.  The following binary
                    339: will work on both pmax and arc machines.
1.59      sthen     340: <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/2.2/pmax/ld.so">
1.1       deraadt   341: The replacement binary is here</a>.
                    342: <p>
                    343: </ul>
1.41      henning   344: <a name="arc"></a>
                    345: <h3><font color="#e00000">arc</font></h3>
1.1       deraadt   346: <ul>
1.37      naddy     347: <li><font color="#009000"><strong>SECURITY FIX</strong></font><br>
1.1       deraadt   348: A security problem in the shared library linker <strong>ld.so</strong> requires
                    349: that you replace it with a new binary.  The following binary
                    350: will work on both pmax and arc machines.
1.59      sthen     351: <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/2.2/pmax/ld.so">
1.1       deraadt   352: The replacement binary is here</a>.
                    353: <p>
                    354: </ul>
1.41      henning   355: <h3><font color="#e00000">alpha</font></h3>
1.1       deraadt   356: <p>
                    357: <ul>
1.37      naddy     358: <li><font color="#009000"><strong>MISSING FUNCTIONALITY</strong></font><br>
1.4       deraadt   359: Network Address Translation and other parts of IP Filtering do not work
1.1       deraadt   360: on the alpha.  This will be fixed in the 2.3 release, and perhaps earlier
                    361: in a snapshot.  There is no patch for 2.2.
                    362: <p>
                    363: </ul>
1.41      henning   364: <h3><font color="#e00000">hp300</font></h3>
1.1       deraadt   365: <p>
                    366: <ul>
                    367: <li>No problems identified yet.
                    368: <p>
                    369: </ul>
1.41      henning   370: <h3><font color="#e00000">mvme68k</font></h3>
1.1       deraadt   371: <ul>
                    372: <li>No problems identified yet.
                    373: <p>
1.64      deraadt   374:
1.1       deraadt   375: </ul>
1.17      deraadt   376:
1.1       deraadt   377: <hr>
1.16      deraadt   378: <a href=index.html><img height=24 width=24 src=back.gif border=0 alt=OpenBSD></a>
1.37      naddy     379: <a href="mailto:www@openbsd.org">www@openbsd.org</a>
1.65    ! deraadt   380: <br><small>$OpenBSD: errata22.html,v 1.64 2012/10/27 14:45:05 deraadt Exp $</small>
1.1       deraadt   381:
                    382: </body>
                    383: </html>