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