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

Annotation of www/errata22.html, Revision 1.97

1.95      bentley     1: <!doctype html>
                      2: <html lang=en id=errata>
                      3: <meta charset=utf-8>
                      4:
1.85      tj          5: <title>OpenBSD 2.2 Errata</title>
1.1       deraadt     6: <meta name="description" content="the OpenBSD CD errata page">
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.87      tb          9: <link rel="canonical" href="https://www.openbsd.org/errata22.html">
1.1       deraadt    10:
1.76      deraadt    11: <!--
                     12:                        IMPORTANT REMINDER
                     13:        IF YOU ADD A NEW ERRATUM, MAIL THE PATCH TO TECH AND ANNOUNCE
                     14: -->
                     15:
1.1       deraadt    16:
1.95      bentley    17: <h2 id=OpenBSD>
1.84      deraadt    18: <a href="index.html">
1.95      bentley    19: <i>Open</i><b>BSD</b></a>
                     20: 2.2 Errata
1.85      tj         21: </h2>
1.84      deraadt    22: <hr>
1.1       deraadt    23:
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.69      deraadt    40: <a href="errata37.html">3.7</a>,
1.54      deraadt    41: <br>
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>,
1.66      deraadt    57: <a href="errata53.html">5.3</a>,
1.69      deraadt    58: <br>
1.67      deraadt    59: <a href="errata54.html">5.4</a>,
1.75      jsg        60: <a href="errata55.html">5.5</a>,
1.79      deraadt    61: <a href="errata56.html">5.6</a>,
1.82      deraadt    62: <a href="errata57.html">5.7</a>,
1.83      deraadt    63: <a href="errata58.html">5.8</a>,
1.86      deraadt    64: <a href="errata59.html">5.9</a>,
1.89      tj         65: <a href="errata60.html">6.0</a>,
1.91      deraadt    66: <a href="errata61.html">6.1</a>,
1.92      deraadt    67: <a href="errata62.html">6.2</a>,
1.93      deraadt    68: <a href="errata63.html">6.3</a>,
1.94      deraadt    69: <a href="errata64.html">6.4</a>,
                     70: <a href="errata65.html">6.5</a>.
1.2       deraadt    71: <hr>
                     72:
1.21      ericj      73: <p>
1.89      tj         74: Patches for the OpenBSD base system are distributed as unified diffs.
                     75: Each patch contains usage instructions.
                     76: All the following patches are also available in one
                     77: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.2.tar.gz">tar.gz file</a>
                     78: for convenience.
1.70      deraadt    79:
                     80: <p>
1.89      tj         81: Patches for supported releases are also incorporated into the
1.90      tj         82: <a href="stable.html">-stable branch</a>.
1.21      ericj      83:
1.11      deraadt    84: <hr>
                     85:
1.1       deraadt    86: <ul>
1.96      deraadt    87:
1.77      bentley    88: <li id="ipsec">
1.96      deraadt    89: <strong>001: SECURITY FIX</strong>
1.73      deraadt    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.88      tb         94: <a href="https://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.96      deraadt    97:
1.77      bentley    98: <li id="xterm-xaw">
1.96      deraadt    99: <strong>002: SECURITY FIX</strong>
1.73      deraadt   100: &nbsp; <i>All architectures</i><br>
1.5       matthieu  101: As stated in CERT advisory VB-98.04, there are buffer
1.95      bentley   102: overrun problems in <b>xterm</b> related to the input-Method,
1.8       deraadt   103: preeditType, and *Keymap resources. Additional buffer overruns exist in
1.95      bentley   104: the <b>Xaw</b> library related to the inputMethod and
1.8       deraadt   105: preeditType resources.   The xterm(1) problem represents a security
                    106: vulnerability for any platform where xterm is installed setuid-root
                    107: (as is the case for all OpenBSD platforms).  The Xaw problem represents
                    108: a security vulnerability for any setuid-root program that uses the Xaw
                    109: library (including xterm).  Patch1 from XFree86 3.3.2 corrects
                    110: these problems.
1.88      tb        111: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.2/common/xterm-xaw.patch">
1.6       deraadt   112: We provide a version of this patch file specifically for the OpenBSD 2.2 tree</a>.
1.5       matthieu  113: <p>
1.96      deraadt   114:
1.77      bentley   115: <li id="rmjob">
1.96      deraadt   116: <strong>003: SECURITY FIX</strong>
1.73      deraadt   117: &nbsp; <i>All architectures</i><br>
1.1       deraadt   118: An exploitable buffer mismanagement exists in a subroutine used by
                    119: lprm and lpd.  The problem is exploitable by users on a particular
1.95      bentley   120: machine if there is an entry in <b>/etc/printcap</b> which
1.1       deraadt   121: points at a remote printer.
1.88      tb        122: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.2/common/rmjob.patch">
1.1       deraadt   123: A patch is available which corrects this behaviour</a>.
                    124: <p>
1.96      deraadt   125:
1.77      bentley   126: <li id="uucpd">
1.96      deraadt   127: <strong>004: SECURITY FIX</strong>
1.73      deraadt   128: &nbsp; <i>All architectures</i><br>
1.1       deraadt   129: A DNS-based vulnerability exists when uucpd is used.  By default uucpd
                    130: is not enabled in the OpenBSD releases, but some sites may have enabled it.
1.88      tb        131: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.2/common/uucpd.patch">
1.1       deraadt   132: A patch is available which corrects this behaviour</a>.
                    133: <p>
1.96      deraadt   134:
1.77      bentley   135: <li id="named">
1.96      deraadt   136: <strong>005: SECURITY FIX</strong>
1.73      deraadt   137: &nbsp; <i>All architectures</i><br>
1.1       deraadt   138: A vulnerability exists when (and only when) /etc/named.conf has the
1.95      bentley   139: <b>fake-iquery</b> option enabled.
1.88      tb        140: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.2/common/named.patch">
1.1       deraadt   141: A patch is available which corrects this behaviour</a>.
                    142: <p>
1.96      deraadt   143:
1.77      bentley   144: <li id="ping">
1.96      deraadt   145: <strong>006: SECURITY FIX</strong>
1.73      deraadt   146: &nbsp; <i>All architectures</i><br>
1.1       deraadt   147: A vulnerability exists in ping(8); if the -R option is used to record
                    148: routes, an attacker can spoof a reply packet that will overflow inside
                    149: ping.  Preliminary investigation makes it look the worst attack
                    150: possible is to make ping crash, but one never knows...
1.88      tb        151: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.2/common/ping.patch">
1.1       deraadt   152: A patch is available which corrects this behaviour</a>.
                    153: <p>
1.96      deraadt   154:
1.77      bentley   155: <li id="sourceroute">
1.96      deraadt   156: <strong>007: SECURITY FIX</strong> &nbsp; <i>All architectures</i><br>
1.95      bentley   157: If the sysctl variable <b>net.inet.ip.forwarding</b> is
                    158: enabled (value 1), but the variable <b>net.inet.ip.sourceroute</b>
1.1       deraadt   159: is disabled (value 0), the kernel will block source routed packets from
                    160: going through, but will still accept source routing packets destined for
1.95      bentley   161: itself.  Our fix changes the <b>net.inet.ip.sourceroute</b>
1.1       deraadt   162: variable semantics to mean that all source routed packets should
                    163: be blocked completely.
1.88      tb        164: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.2/common/sourceroute.patch">
1.1       deraadt   165: A kernel patch is provided</a>.
                    166: <p>
1.96      deraadt   167:
1.77      bentley   168: <li id="ruserok">
1.96      deraadt   169: <strong>008: SECURITY FIX</strong>
1.73      deraadt   170: &nbsp; <i>All architectures</i><br>
1.1       deraadt   171: A combination localhost+remote host security problem exists if a
1.26      jsyn      172: local user running a setuid binary causes a non-existent root .rhosts
1.1       deraadt   173: file to be created via a symbolic link with a specific kind of corefile,
                    174: and then subsequently uses rsh/rlogin to enter the machine from remote.
                    175: A similar exploit might also be possible using sshd which lacks any code
                    176: for checking for deviations from the expected format in the .rhosts or
                    177: .shosts files, but we have not confirmed this yet.  The following two
                    178: fixes are recommended:
                    179: <p>
                    180: <ul>
                    181: <li>
1.88      tb        182: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.2/common/nosuidcoredump.patch">
1.1       deraadt   183: (1) A kernel patch which adds a new sysctl option which permits the
                    184: administrator to decide whether setuid corefiles should be written or not</a>.
                    185: <p>
1.88      tb        186: <li><a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.2/common/rcmd.patch">
1.1       deraadt   187: (2) Replaces the libc ruserok() function with a more paranoid
                    188: version which detects bogus looking .rhosts files better.</a>
                    189: </ul>
                    190: <p>
                    191: If the
                    192: first patch is used to stop setuid coredumps, then the second patch is
                    193: not as important.
                    194: This problem is fixed much better in OpenBSD-current, where the kernel's
                    195: symbolic link handling has been improved such that coredumping will not
                    196: create a file on the other side of a symbolic link.  Such a patch is not
                    197: possible for the 4.4lite1 VFS layer in the OpenBSD 2.2 kernel.<p>
                    198: The problem with the ruserok() function appears to also exist in
                    199: ssh 1.2.21 and previous (the ssh people have been alerted).
                    200: <p>
1.96      deraadt   201:
1.77      bentley   202: <li id="mmap">
1.96      deraadt   203: <strong>009: SECURITY FIX</strong> &nbsp; <i>All architectures</i><br>
1.1       deraadt   204: A bug in the vm system permits a file descriptor opened read-only on a
                    205: device, to later on be mmap(2)'d read-write, and then modified.  This
                    206: does not result in a security hole by itself, but it does violate the
                    207: safety semantics which securelevels are supposed to provide.  If a user
                    208: manages to gain kmem group permissions, using this problem they can then
                    209: gain root trivially and/or turn securelevels off.
1.88      tb        210: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.2/common/vm_mmap.patch">
1.1       deraadt   211: A kernel patch is available which corrects this behaviour (this is
                    212: revision 3 of this patch)</a>.
                    213: <p>
1.97    ! deraadt   214:
        !           215: <li id="build1">
        !           216: <strong>010: BUILD PROCESS FIX</strong>
1.73      deraadt   217: &nbsp; <i>All architectures</i><br>
1.1       deraadt   218: Building an object tree from a read-only source tree (such as off a CDROM)
                    219: may fail under certain circumstances (e.g. when creating a symlink on sparc
                    220: whose target name is exactly 33 characters).  As a workaround you have to
                    221: either provide the source tree read/write, or install a newer version of
1.67      deraadt   222: /usr/bin/readlink.
1.88      tb        223: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.2/common/readlink.c">
1.1       deraadt   224: A replacement source file exists</a>.
                    225: <p>
1.96      deraadt   226:
1.77      bentley   227: <li id="mountd">
1.96      deraadt   228: <strong>011: SECURITY FIX</strong>
1.73      deraadt   229: &nbsp; <i>All architectures</i><br>
1.1       deraadt   230: If a line in /etc/exports which contains hostnames results in an empty
                    231: list because none of the supplied hostnames is known, mountd(8) will
                    232: accidentally export the filesystem to the world.
1.88      tb        233: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.2/common/mountd.patch">
1.1       deraadt   234: A patch is available which corrects this behaviour</a>.
                    235: <p>
1.97    ! deraadt   236:
        !           237: <li id="eor">
        !           238: <strong>012: RELIABILITY FIX</strong>
1.73      deraadt   239: &nbsp; <i>All architectures</i><br>
1.1       deraadt   240: Setting the MSG_EOR flag on a tcp packet in the send(2) family of
                    241: system calls could cause a kernel panic.
1.88      tb        242: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.2/common/send.patch">
1.1       deraadt   243: A patch</a> to return EINVAL in this case is available.
                    244: <p>
1.96      deraadt   245:
1.77      bentley   246: <li id="f00f">
1.96      deraadt   247: <strong>013: RELIABILITY FIX</strong><br>
1.26      jsyn      248: The Intel P5 F00F bug was discovered after the CDRs had already been
1.1       deraadt   249: sent to the manufacturer.  This problem permits any user who has an account
                    250: to lock your machine up using a 4-line program.  The problem only affects
                    251: Intel P5 processors (the i386, i486, P-Pro, and P-II are not vulnerable,
                    252: nor are processors by other manufacturers).
1.88      tb        253: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.2/i386/f00f.patch">
1.1       deraadt   254: A kernel source-code patch is available</a>.
                    255: <p>
1.97    ! deraadt   256:
        !           257: <li id="svr4">
        !           258: <strong>014: FUNCTIONALITY FIX</strong><br>
1.1       deraadt   259: Some Linux binaries will execute in SVR4 emulation mode, which is
1.12      aaron     260: definitely a problem for people who need Linux emulation to work correctly.
1.1       deraadt   261: To solve this mis-identification problem,
1.88      tb        262: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.2/i386/compat_linux.patch">
1.1       deraadt   263: a patch file is provided</a>.
                    264: <p>
1.97    ! deraadt   265:
        !           266: <li li="apm">
        !           267: <strong>015: RELIABILITY FIX</strong><br>
1.1       deraadt   268: APM can crash on machines without it.
1.88      tb        269: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.2/i386/apm.patch">
1.1       deraadt   270: A kernel source-code patch is available</a>.
                    271: <p>
1.97    ! deraadt   272:
        !           273: <li li="ide">
        !           274: <strong>016: INSTALLATION PROCESS FLAW</strong><br>
1.25      pvalchev  275: A few people are running into this problem, particularly if they had some
1.1       deraadt   276: other *BSD operating system on their machine before trying OpenBSD: if after
                    277: installation onto an IDE-based machine, the kernel fails to mount the root
                    278: partition because it thinks that it should be opening sd0 (0x400), this means
                    279: you have incorrectly setup your disklabel for the IDE drive -- the disklabel
                    280: is indicating that the drive is SCSI.
                    281: To repair this, use the floppy to run "disklabel -E wd0", then using the
                    282: "edit" command ensure the type field is set to "ST506".
                    283: <p>
1.97    ! deraadt   284:
        !           285: <li id="mac68kx">
        !           286: <strong>017: NEW SOFTWARE</strong><br>
1.1       deraadt   287: Unfortunately, X11 binaries for the mac68k did not manage to make it onto the
                    288: CDROM.  However, X11 for the mac68k is immediately available from
1.88      tb        289: <a href="https://ftp.openbsd.org/pub/OpenBSD/2.2/mac68k/X11/X11R6.tar.gz">
                    290: https://ftp.OpenBSD.org/pub/OpenBSD/2.2/mac68k/X11/X11R6.tar.gz</a>.  Please
                    291: be sure to read the <a href="https://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   292: and setting up X.
                    293: <p>
1.97    ! deraadt   294:
        !           295: <li id="mac68kpath">
        !           296: <strong>018: INSTALLATION PROCESS FLAW</strong><br>
1.1       deraadt   297: As shipped on the CDROM, both the
1.88      tb        298: <a href="https://ftp.openbsd.org/pub/OpenBSD/2.2/mac68k/bsd-generic.tar.gz">
1.1       deraadt   299: generic kernel</a>
                    300: and the
1.88      tb        301: <a href="https://ftp.openbsd.org/pub/OpenBSD/2.2/bsd-genericbsc.tar.gz">
1.1       deraadt   302: genericsbc kernel</a>
                    303: extract themselves into the wrong place in the filesystem.
1.95      bentley   304: Both <em>should</em> extract a kernel named <code>/bsd</code>, but they extract
                    305: the kernel into <code>/usr/src/sys/arch/mac68k/compile</code> instead.
1.1       deraadt   306: <p>
                    307: This has been fixed on the ftp release of <a href=22.html>OpenBSD 2.2</a>, and
1.88      tb        308: fresh kernels are available from <a href="https://ftp.openbsd.org/pub/OpenBSD/2.2/mac68k">
1.59      sthen     309: http://ftp.OpenBSD.ORG/pub/OpenBSD/2.2/mac68k/</a>.  If at all possible,
1.1       deraadt   310: installing these kernels is recommended.
                    311: <p>
                    312: A number of possible workarounds exist if you don't have easy access to ftp
                    313: the updated kernels.  The simplest of these is to use a
                    314: MacOS program to uncompress and untar the kernel aad use the Installer's
                    315: mini-shell to "cpin" the kernel.  Alternately, you could install the kernel
1.95      bentley   316: with the Installer and use the mini-shell to move the binary from <code>/usr/src/...</code> to <code>/bsd</code>.
1.1       deraadt   317: <p>
1.97    ! deraadt   318:
        !           319: <li id="4300">
        !           320: <strong>019: RELIABILITY FIX</strong><br>
1.25      pvalchev  321: Older 4/xxx systems (particularly the 4/300's) cannot boot
1.1       deraadt   322: with the 2.2 kernel due to bugs in the scsi device driver.
1.88      tb        323: <a href="https://ftp.OpenBSD.org/pub/OpenBSD/patches/2.2/sparc/esp.patch">
1.1       deraadt   324: A kernel source patch is available</a>.
                    325: Replacement kernels are available for:
1.88      tb        326: <a href="https://ftp.OpenBSD.org/pub/OpenBSD/patches/2.2/sparc/bsd">bsd</a>,
                    327: <a href="https://ftp.OpenBSD.org/pub/OpenBSD/patches/2.2/sparc/bsd.scsi3">bsd.scsi3</a>,
1.1       deraadt   328: and a replacement for bsd.rd is coming soon.
                    329: <p>
1.96      deraadt   330:
1.77      bentley   331: <li id="sparciommu">
1.96      deraadt   332: <strong>020: RELIABILITY FIX</strong><br>
1.1       deraadt   333: SPARCstation 4 and 5 (Microsparc 2) users may see kernel panics when
                    334: using a custom kernel configured for option sun4m only.
1.88      tb        335: <a href="https://ftp.OpenBSD.org/pub/OpenBSD/patches/2.2/sparc/sun4m.patch">
1.1       deraadt   336: A workaround (kernel source patch) is available</a>.  Apply the patch and
                    337: then re-build your kernel.
                    338: <p>
1.97    ! deraadt   339:
        !           340: <li id="xamiga">
        !           341: <strong>021: FUNCTIONALITY FIX</strong><br>
1.1       deraadt   342: Missing Xamiga manual pages.  Get
1.88      tb        343: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.2/amiga/Xamiga-manual.tgz">
1.1       deraadt   344: this package</a> and execute, <i>as root</i>:<br>
1.95      bentley   345: <b><b># </b>pkg_add Xamiga-manual.tgz</b><br>
1.1       deraadt   346: The MD5 checksum of this package is:<br>
1.96      deraadt   347: <b>MD5 (Xamiga-manual.tgz) = 2362a7857264b9d17f65cca258b42031</b>
                    348: <p>
1.97    ! deraadt   349:
        !           350: <li id="araidne">
        !           351: <strong>022: FUNCTIONALITY FIX</strong><br>
1.1       deraadt   352: The Ariadne ethernet support was broken, there will be both binary and
                    353: source level fixes available shortly.  If you are in a hurry mail
1.37      naddy     354: <a href="mailto:niklas@openbsd.org">Niklas</a> for a test kernel.<p>
1.72      deraadt   355: <p>
1.97    ! deraadt   356:
        !           357: <li id="pmax">
        !           358: <strong>023: FUNCTIONALITY FIX</strong><br>
1.67      deraadt   359: There is a Year-1998 problem in the time-setting code (which causes the
1.1       deraadt   360: date and time to be set incorrectly after a reboot in 1998).
1.88      tb        361: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.2/pmax/clock.patch">
1.1       deraadt   362: A source code patch file is available</a> plus replacement installation
                    363: kernels for the 2.2 release at
1.88      tb        364: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.2/pmax/bsd.NFS">bsd.NFS</a>,
                    365: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.2/pmax/bsd">bsd</a>,
                    366: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.2/pmax/bsd.rz0">bsd.rz0</a>.
1.1       deraadt   367: <p>
1.97    ! deraadt   368:
        !           369: <li id="3min">
        !           370: <strong>024: FUNCTIONALITY FIX</strong><br>
1.1       deraadt   371: X11 support for the 3min and 3maxplus machines was broken
                    372: due to a kernel bug.
1.88      tb        373: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.2/pmax/fb.patch">
1.1       deraadt   374: A source code patch is available</a>.
                    375: <p>
1.96      deraadt   376:
1.77      bentley   377: <li id="ldso">
1.96      deraadt   378: <strong>025: SECURITY FIX</strong><br>
1.95      bentley   379: A security problem in the shared library linker <b>ld.so</b>
1.1       deraadt   380: requires that you replace it with a new binary.  The following binary
                    381: will work on both pmax and arc machines.
1.88      tb        382: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.2/pmax/ld.so">
1.1       deraadt   383: The replacement binary is here</a>.
                    384: <p>
1.97    ! deraadt   385:
        !           386: <li id="ldso2">
        !           387: <strong>026: SECURITY FIX</strong><br>
1.95      bentley   388: A security problem in the shared library linker <b>ld.so</b> requires
1.1       deraadt   389: that you replace it with a new binary.  The following binary
                    390: will work on both pmax and arc machines.
1.88      tb        391: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.2/pmax/ld.so">
1.1       deraadt   392: The replacement binary is here</a>.
                    393: <p>
1.97    ! deraadt   394:
        !           395: <li id="nat">
        !           396: <strong>027: MISSING FUNCTIONALITY</strong><br>
1.4       deraadt   397: Network Address Translation and other parts of IP Filtering do not work
1.1       deraadt   398: on the alpha.  This will be fixed in the 2.3 release, and perhaps earlier
                    399: in a snapshot.  There is no patch for 2.2.
                    400: <p>
1.86      deraadt   401:
1.1       deraadt   402: </ul>
1.64      deraadt   403:
1.78      tedu      404: <hr>