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