Annotation of www/errata27.html, Revision 1.2
1.1 deraadt 1: <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML Strict//EN">
2: <html>
3: <head>
4: <title>OpenBSD 2.7 errata</title>
5: <link rev=made href=mailto:www@openbsd.org>
6: <meta name="resource-type" content="document">
7: <meta name="description" content="the OpenBSD CD errata page">
8: <meta name="keywords" content="openbsd,cd,errata">
9: <meta name="distribution" content="global">
10: <meta name="copyright" content="This document copyright 1997-1998 by OpenBSD.">
11: </head>
12:
13: <BODY BGCOLOR="#FFFFFF" TEXT="#000000" LINK="#23238E">
14:
15: <img alt="[OpenBSD]" height=30 width=141 SRC="images/smalltitle.gif">
16: <h2><font color=#0000e0>
17: This is the OpenBSD 2.7 release errata & patch list:
18:
19: </font></h2>
20:
21: <hr>
22: <a href=stable.html>For OpenBSD patch branch information, please refer here.</a><br>
23: <a href=errata21.html>For 2.1 errata, please refer here</a>.<br>
24: <a href=errata22.html>For 2.2 errata, please refer here</a>.<br>
25: <a href=errata23.html>For 2.3 errata, please refer here</a>.<br>
26: <a href=errata24.html>For 2.4 errata, please refer here</a>.<br>
27: <a href=errata25.html>For 2.5 errata, please refer here</a>.<br>
28: <a href=errata26.html>For 2.6 errata, please refer here</a>.<br>
29: <a href=errata27.html>For 2.7 errata, please refer here</a>.<br>
30: <a href=errata.html>For 2.8 errata, please refer here</a>.<br>
31: <hr>
32:
33: <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.7.tar.gz>
34: You can also fetch a tar.gz file containing all the following patches</a>.
35: This file is updated once a day.
36:
37: <p> The patches below are available in CVS via the
38: <code>OPENBSD_2_7</code> <a href="stable.html">patch branch</a>.
39:
40: <p>
41: For more detailed information on install patches to OpenBSD, please
42: consult the <a href="./faq/faq10.html#10.14">OpenBSD FAQ</a>.
43: <hr>
44:
45: <dl>
46: <a name=all></a>
47: <li><h3><font color=#e00000>All architectures</font></h3>
48: <ul>
1.2 ! aaron 49: <a name=execsubr> </a>
! 50: <li><font color=#009000><strong>033: RELIABILITY FIX: Nov 6, 2000</strong></font><br>
! 51: Invalid fields in the exec header could cause a crash.<br>
! 52: <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.7/common/033_execsubr.patch>
! 53: A source code patch exists which remedies this problem.</a>
! 54: <p>
1.1 deraadt 55: <a name=xtrans> </a>
56: <li><font color=#009000><strong>032: SECURITY FIX: Oct 26, 2000</strong></font><br>
57: There are two possibly exploitable potential buffer overflows in the X11
58: libraries using the xtrans code. One of these vulnerabilities was
59: reported to the
60: <a href="http://www.securityfocus.com/archive/1/139436">BUGTRAQ</a>
61: mailing list.
62: <br>
63: <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.7/common/032_xtrans.patch>
64: A source code patch exists which remedies this problem.</a>
65: <p>
66: <a name=httpd></a>
67: <li><font color=#009000><strong>031: SECURITY FIX: Oct 18, 2000</strong></font><br>
68: Apache has several bugs in <tt>mod_rewrite</tt> and <tt>mod_vhost_alias</tt>
69: that could cause arbirtary files accessible to the www user on the server
70: to be exposed under certain configurations when these modules are used.
71: (These modules are not active by default).
72: <br>
73: <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.7/common/031_httpd.patch>
74: A source code patch exists which remedies this problem.</a>
75: <p>
76: <a name=telnetd></a>
77: <li><font color=#009000><strong>030: SECURITY FIX: Oct 10, 2000</strong></font><br>
78: The telnet daemon does not strip out the TERMINFO, TERMINFO_DIRS, TERMPATH
79: and TERMCAP (when it starts with a '/') environment variables.
80: <br>
81: <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.7/common/030_telnetd.patch>
82: A source code patch exists which remedies this problem.</a>
83: <p>
84: <a name=sendmail></a>
85: <li><font color=#009000><strong>029: RELIABILITY FIX: Oct 9, 2000</strong></font><br>
86: There is a non-exploitable buffer overflow in sendmail's test mode.
87: <br>
88: <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.7/common/029_sendmail.patch>
89: A source code patch exists which remedies this problem.</a>
90: <p>
91: <a name=format_strings></a>
92: <li><font color=#009000><strong>028: SECURITY FIX: Oct 6, 2000</strong></font><br>
93: There are printf-style format string bugs in several privileged programs.
94: <br>
95: <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.7/common/028_format_strings.patch>
96: A source code patch exists which remedies this problem.</a>
97: <p>
98: <a name=curses></a>
99: <li><font color=#009000><strong>027: SECURITY FIX: Oct 6, 2000</strong></font><br>
100: libcurses honored terminal descriptions in the $HOME/.terminfo directory
101: as well as in the TERMCAP environment variable for setuid and setgid
102: applications.
103: <br>
104: <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.7/common/027_curses.patch>
105: A source code patch exists which remedies this problem.</a>
106: <p>
107: <a name=talkd></a>
108: <li><font color=#009000><strong>026: SECURITY FIX: Oct 6, 2000</strong></font><br>
109: A format string vulnerability exists in talkd(8). It is not clear
110: yet what the impact is.
111: <br>
112: <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.7/common/026_talkd.patch>
113: A source code patch exists which remedies this problem.</a>
114: <p>
115: <a name=pw_error></a>
116: <li><font color=#009000><strong>025: SECURITY FIX: Oct 3, 2000</strong></font><br>
117: A format string vulnerability exists in the pw_error(3) function. This
118: manifests itself as a security hole in the chpass utility. As a workaround
119: which disables its functionality, do
120: <pre>
121: # chmod u-s /usr/bin/chpass
122: </pre>
123: <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.7/common/025_pw_error.patch>
124: A source code patch exists which remedies this problem.</a>
125: <p>
126: <a name=ipsec></a>
127: <li><font color=#009000><strong>024: SECURITY FIX: Sep 18, 2000</strong></font><br>
128: Bad ESP/AH packets could cause a crash under certain conditions.
129: <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.7/common/024_ipsec.patch><br>
130: A source code patch exists which remedies this problem.</a>
131: <p>
132: <a name=xlock></a>
133: <li><font color=#009000><strong>023: SECURITY FIX: Aug 16, 2000</strong></font><br>
134: A format string vulnerability exists in xlock. As a workaround which disables
135: its functionality, do
136: <pre>
137: # chmod u-s /usr/X11R6/bin/xlock
138: </pre>
139: <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.7/common/023_xlock.patch>
140: A source code patch exists which remedies this problem.</a>
141: <p>
142: <a name=X11_libs></a>
143: <li><font color=#009000><strong>021: SECURITY FIX: July 14, 2000</strong></font><br>
144: Various problems in X11 libraries have various side effects. We provide a
145: jumbo patch to fix them.<p>
146: <ul>
147: <li><a href="http://www.securityfocus.com/templates/archive.pike?list=1&date=2000-05-15&msg=Pine.LNX.4.21.0005181947210.17658-100000@ferret.lmh.ox.ac.uk">
148: Nasty X Server Dos</a><br>
149: This is fixed by the patch to <b>xc/programs/Xsever/os/secauth.c</b>.
150: <li><a href="http://www.securityfocus.com/templates/archive.pike?list=1&date=2000-06-15&msg=Pine.LNX.4.21.0006192251480.9945-100000@ferret.lmh.ox.ac.uk">
151: Various nasty libX11 holes</a><br>
152: This is covered by the patches to <b>xc/lib/X11</b>.
153: <li><a href="http://www.securityfocus.com/templates/archive.pike?list=1&date=2000-06-15&msg=Pine.LNX.4.21.0006192220220.9945-100000@ferret.lmh.ox.ac.uk">
154: libICE DoS</a><br>
155: This is covered by the patches to <b>xc/lib/ICE</b>.
156: <li><a href="http://www.securityfocus.com/templates/archive.pike?list=1&date=2000-04-15&msg=Pine.LNX.4.10.10004161835150.863-100000@localhost">
157: Server overflow</a><br>
158: This is covered by the patches to <b>xc/programs/Xserver/xkb</b>.
159: <br>
160: Note that the default OpenBSD install is not vulnerable to this, since the
161: the XFree86 Xwrapper already has tests for bad arguments.
162: </ul>
163: <br>
164: <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.7/common/021_X11_libs.patch>
165: A source code patch exists which remedies these problems.</a><br>
166: <strong>Note 1:</strong> tcl/tk is required to build X11 from source.<br>
167: <strong>Note 2:</strong> When re-building use the command
168: `make DESTDIR=/ build' or you will get an error in the last
169: step of the build (makewhatis). If you forget to set DESTDIR you can
170: ignore the build error. The whatis database will be rebuilt the next
171: time /etc/weekly runs.
172: <p>
173: <a name=ftpd></a>
174: <li><font color=#009000><strong>019: SECURITY FIX: July 5, 2000</strong></font><br>
175: Just like pretty much all the other unix ftp daemons on the planet,
176: ftpd had a remote root hole in it. Luckily, ftpd was not enabled by default.
177: The problem exists if anonymous ftp is enabled.
178: <br>
179: <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.7/common/019_ftpd.patch>
180: A source code patch exists which remedies this problem.</a>
181: <p>
182: <a name=mopd></a>
183: <li><font color=#009000><strong>018: SECURITY FIX: July 5, 2000</strong></font><br>
184: Mopd contained a buffer overflow.
185: <br>
186: <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.7/common/018_mopd.patch>
187: A source code patch exists which remedies this problem.</a>
188: <p>
189: <a name=screen></a>
190: <li><font color=#009000><strong>017: INSTALLATION FIX: July 3, 2000</strong></font>
191: <br>
192: The screen package shipped with 2.7 does not install itself properly. The
193: existing package in 2.7/packages/_ARCH_/screen-3.9.5.tgz has been renamed to
194: screen-3.9.5.tgz.old and a replacement package has been provided under the
195: name screen-3.9.5p1.tgz.
196: <br>
197: <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.7/ports/017_screen.patch>
198: A source code patch exists which remedies this problem.</a>
199: <p>
200: <a name=libedit></a>
201: <li><font color=#009000><strong>013: SECURITY FIX: June 28, 2000</strong></font><br>
202: libedit would check for a <b>.editrc</b> file in the current directory.
203: That behaviour is not nice; this does not turn into a security problem in
204: any real world situation that we know of, but a patch is available anyways.
205: <br>
206: <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.7/common/013_libedit.patch>
207: A source code patch exists which remedies this problem.</a>
208: <p>
209: <a name=dhclient></a>
210: <li><font color=#009000><strong>012: SECURITY FIX: June 24, 2000</strong></font><br>
211: A serious bug in dhclient(8) could allow strings from a malicious dhcp
212: server to be executed in the shell as root.
213: <br>
214: <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.7/common/012_dhclient.patch>
215: A source code patch exists which remedies this problem.</a>
216: <p>
217: <a name=isakmpd></a>
218: <li><font color=#009000><strong>009: SECURITY FIX: June 9, 2000</strong></font><br>
219: A serious bug in isakmpd(8) policy handling wherein policy
220: verification could be completely bypassed in isakmpd.
221: <br>
222: <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.7/common/009_isakmpd.patch>
223: A source code patch exists which remedies this problem.</a>
224: <p>
225: <a name=msdosfs></a>
226: <li><font color=#009000><strong>008: RELIABILITY FIX: June 8, 2000</strong></font><br>
227: Some operations in msdosfs could result in a system panic.
228: <br>
229: <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.7/common/008_msdosfs.patch>
230: A source code patch exists which remedies this problem.</a>
231: <p>
232: <a name=cd9660></a>
233: <li><font color=#009000><strong>007: RELIABILITY FIX: June 8, 2000</strong></font><br>
234: NFS exporting of CD filesystems caused a system panic.
235: <br>
236: <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.7/common/007_cd9660.patch>
237: A source code patch exists which remedies this problem.</a>
238: <p>
239: <a name=uselogin></a>
240: <li><font color=#009000><strong>006: SECURITY FIX: June 6, 2000</strong></font><br>
241: The non-default UseLogin feature in <b>/etc/sshd_config</b> is broken and should not
242: be used. On other operating systems, it results in a hole.<br>
243: Avoid use of this feature, or update to OpenSSH 2.1.1 or later if you must use it.
244: <p>
245: <a name=ipopts></a>
246: <li><font color=#009000><strong>005: RELIABILITY FIX: May 29, 2000</strong></font><br>
247: Parse IPv4 options more carefully. It is not yet clear if this can even be used
248: to crash the machine remote or locally.
249: <br>
250: <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.7/common/005_ipopts.patch>
251: A source code patch exists which remedies this problem.</a>
252: <p>
253: <a name=route></a>
254: <li><font color=#009000><strong>004: RELIABILITY FIX: May 29, 2000</strong></font><br>
255: Certain routing table modifications by the superuser could cause a system panic.
256: <br>
257: <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.7/common/004_route.patch>
258: A source code patch exists which remedies this problem.</a>
259: <p>
260: <a name=bridge></a>
261: <li><font color=#009000><strong>003: SECURITY FIX: May 26, 2000</strong></font><br>
262: It is possible to bypass the <i>learning</i> flag on an interface if frames
263: go directly to the machine acting as a
264: <a href="http://www.openbsd.org/cgi-bin/man.cgi?query=bridge&sektion=4">bridge</a>.
265: <br>
266: <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.7/common/003_bridge.patch>
267: A source code patch exists which remedies this problem.</a>
268: <p>
269: <a name=ef></a>
270: <li><font color=#009000><strong>002: DRIVER FIX: May 26, 2000</strong></font><br>
271: The
272: <a href="http://www.openbsd.org/cgi-bin/man.cgi?query=ef&sektion=4">ef(4)</a>
273: driver will complain when adding an address with ifconfig
274: (ifconfig: SIOCAIFADDR: Invalid argument).<br>
275: <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.7/common/002_ef.patch>
276: A source code patch exists which remedies this problem.</a>
277: <p>
278: <a name=ipf></a>
279: <li><font color=#009000><strong>001: SECURITY FIX: May 25, 2000</strong></font><br>
280: A misuse of
281: <a href="http://www.openbsd.org/cgi-bin/man.cgi?query=ipf&sektion=8">ipf(8)</a>
282: <i>keep-state</i> rules can result in firewall rules being bypassed.<br>
283: <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.7/common/001_ipf.patch>
284: A source code patch exists</a>, which remedies this problem, and updates ipf
285: to version 3.3.16.
286: <p>
287: </ul>
288: <p>
289: <a name=i386></a>
290: <li><h3><font color=#e00000>i386</font></h3>
291: <ul>
292: <a name=xlhash></a>
293: <li><font color=#009000><strong>016: DRIVER BUG: July 2, 2000</strong></font><br>
294: The <a href="http://www.openbsd.org/cgi-bin/man.cgi?query=xl&sektion=4">xl(4)</a>
295: driver supporting various 3com cards, had a bug which prevented the multicast
296: filter from working correctly on the 3c905B, thus preventing many IPv6 things
297: from working.
298: <br>
299: <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.7/i386/016_xlhash.patch>
300: A source code patch exists which remedies this problem.</a>
301: <p>
302: <a name=ste></a>
303: <li><font color=#009000><strong>015: DRIVER BUG: June 30, 2000</strong></font><br>
304: The <a href="http://www.openbsd.org/cgi-bin/man.cgi?query=ste&sektion=4">ste(4)</a>
305: driver supporting Ethernet cards based on the Sundance ST201 chipset
306: (i.e., the D-Link 550TX) has a bug which causes the machine to panic at
307: boot-time.
308: <br>
309: <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.7/i386/015_ste.patch>
310: A source code patch exists which remedies this problem.</a>
311: <p>
312: <a name=pcvt></a>
313: <li><font color=#009000><strong>014: DRIVER BUG: June 30, 2000</strong></font><br>
314: The PC console driver (PCVT) has two bugs. Display problems can result if
315: reverse video mode is turned on or off twice in a row. This patch also
316: fixes a problem with scrolling region handling that has been seen by many
317: users trying to use the BitchX irc client with the screen program.<br>
318: <br>
319: <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.7/i386/014_pcvt.patch>
320: There is now a second revision of the source code patch which remedies this problem.</a>
321: <p>
322: <a name=if_an></a>
323: <li><font color=#009000><strong>011: DRIVER BUG: June 17, 2000</strong></font><br>
324: The <a href="http://www.openbsd.org/cgi-bin/man.cgi?query=an&sektion=4">an(4)</a>
325: Aironet Communications 4500/4800 IEEE 802.11DS driver has a bug which prevents
326: <a href="http://www.openbsd.org/cgi-bin/man.cgi?query=ancontrol&sektion=8">ancontrol(8)</a> from working correctly, instead causing a panic.
327: <br>
328: <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.7/i386/011_an.patch>
329: A source code patch exists which remedies this problem.</a>
330: <p>
331: </ul>
332: <p>
333: <a name=mac68k></a>
334: <li><h3><font color=#e00000>mac68k</font></h3>
335: <ul>
336: <a name=mac68k_arandom></a>
337: <li><font color=#009000><strong>022: INSTALLATION FIX: July 14, 2000</strong></font>
338: <br>
339: The MacOS installer shipped with OpenBSD 2.7 does not correctly make all
340: devices, specifically it does not make the <tt>/dev/arandom</tt> device
341: needed for the userland crypto such as ssh to work. The problem shows itself
342: when ssh-keygen fails to make RSA or DSA keys, resulting in messages like
343: <b>RSA-generate_keys failed</b> or <b>DSA-generate_keys failed</b>.
344: <br>
345: To work around this, once your machine is up and running run the following
346: commands as root:
347: <tt><pre>
348: cd /dev
349: ./MAKEDEV arandom
350: </pre></tt>
351: <p>
352: After doing this (and possibly installing one of the ssl27 packages),
353: reboot your machine and it will generate ssh keys correctly.
354: </ul>
355: <p>
356: <a name=sparc></a>
357: <li><h3><font color=#e00000>sparc</font></h3>
358: <ul>
359: <li>No problems identified yet.
360: </ul>
361: <p>
362: <a name=amiga></a>
363: <li><h3><font color=#e00000>amiga</font></h3>
364: <ul>
365: <a name=amiga_cd></a>
366: <li><font color=#009000><strong>010: CD DISTRIBUTION ERROR: June 15, 2000</strong></font><br>
367: On the 2.7 CD media, the <b>amiga</b> distribution contains two pairs of archives
368: files for installation, ie:
369: <pre>
370: -rw-r--r-- 1 root mirftp 20191465 Apr 29 14:27 base27.tar.gz
371: -rw-r--r-- 1 root mirftp 20291753 May 13 19:33 base27.tgz
372: -rw-r--r-- 1 root mirftp 13699507 Apr 29 14:26 comp27.tar.gz
373: -rw-r--r-- 1 root mirftp 13748096 May 13 19:33 comp27.tgz
374: -rw-r--r-- 1 root mirftp 1005376 Apr 29 14:26 etc27.tar.gz
375: -rw-r--r-- 1 root mirftp 1010772 May 13 19:33 etc27.tgz
376: -rw-r--r-- 1 root mirftp 2755567 Apr 29 14:26 game27.tar.gz
377: -rw-r--r-- 1 root mirftp 2755624 May 13 19:33 game27.tgz
378: -rw-r--r-- 1 root mirftp 5002872 Apr 29 14:26 man27.tar.gz
379: -rw-r--r-- 1 root mirftp 5038896 May 13 19:33 man27.tgz
380: -rw-r--r-- 1 root mirftp 1684356 Apr 29 14:26 misc27.tar.gz
381: -rw-r--r-- 1 root mirftp 1684381 May 13 19:33 misc27.tgz
382: </pre>
383: The installation script will list ALL of these files. For proper
384: operation one should install the <b>*.tgz</b> versions, and deselect
385: the <b>*.tar.gz</b> versions.<br>
386: The FTP area sets do not suffer from this problem.
387: <p>
388: </ul>
389: <p>
390: <a name=pmax></a>
391: <li><h3><font color=#e00000>pmax</font></h3>
392: <ul>
393: <a name=pmax_msgbuf></a>
394: <li><font color=#009000><strong>020: KERNEL BUG: July 10, 2000</strong></font><br>
395: As originally shipped, the pmax port would fail to install due to
396: <b>/kern/msgbuf</b> bugs.<br>
397: The neccessary fixes have been merged,
398: and the binaries needed re-released on the FTP site.<br>
399: However, the 2.7 <b>srcsys.tar.gz</b> file has not been updated.<br>
400: If you recompile a kernel, you should use either the
401: <a href=stable.html>stable release source tree</a> or apply the
402: provided patch to a 2.7 source tree.
403: <br>
404: <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.7/pmax/020_pmax_msgbuf.patch>
405: A source code patch exists which remedies this problem.</a>
406: <p>
407: </ul>
408: <p>
409: <a name=arc></a>
410: <li><h3><font color=#e00000>arc</font></h3>
411: <ul>
412: <li>No problems identified yet.
413: </ul>
414: <p>
415: <a name=alpha></a>
416: <li><h3><font color=#e00000>alpha</font></h3>
417: <ul>
418: <li>No problems identified yet.
419: </ul>
420: <p>
421: <a name=hp300></a>
422: <li><h3><font color=#e00000>hp300</font></h3>
423: <ul>
424: <li>No problems identified yet.
425: </ul>
426: <p>
427: <a name=mvme68k></a>
428: <li><h3><font color=#e00000>mvme68k</font></h3>
429: <ul>
430: <li>No problems identified yet.
431: </ul>
432: <p>
433: <a name=powerpc></a>
434: <li><h3><font color=#e00000>powerpc</font></h3>
435: <ul>
436: <li>No problems identified yet.
437: </ul>
438:
439: </dl>
440: <br>
441:
442: <hr>
443: <a href=stable.html>For OpenBSD patch branch information, please refer here.</a><br>
444: <a href=errata21.html>For 2.1 errata, please refer here</a>.<br>
445: <a href=errata22.html>For 2.2 errata, please refer here</a>.<br>
446: <a href=errata23.html>For 2.3 errata, please refer here</a>.<br>
447: <a href=errata24.html>For 2.4 errata, please refer here</a>.<br>
448: <a href=errata25.html>For 2.5 errata, please refer here</a>.<br>
449: <a href=errata26.html>For 2.6 errata, please refer here</a>.<br>
450: <a href=errata27.html>For 2.7 errata, please refer here</a>.<br>
451: <a href=errata.html>For 2.8 errata, please refer here</a>.<br>
452: <hr>
453:
454: <a href=index.html><img height=24 width=24 src=back.gif border=0 alt=OpenBSD></a>
455: <a href=mailto:www@openbsd.org>www@openbsd.org</a>
1.2 ! aaron 456: <br><small>$OpenBSD: errata27.html,v 1.1 2000/11/02 16:40:40 deraadt Exp $</small>
1.1 deraadt 457:
458: </body>
459: </html>
![[BACK]](/icons/back.gif){kind=icon}
Return to errata27.html CVS log ![[TXT]](/icons/text.gif){kind=icon}
![[DIR]](/icons/dir.gif){kind=icon}
Up to [local] / www