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