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

Annotation of www/errata22.html, Revision 1.84

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