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