Annotation of www/errata26.html, Revision 1.9
1.1 deraadt 1: <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML Strict//EN">
2: <html>
3: <head>
4: <title>OpenBSD 2.6 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.6 release errata & patch list:
18:
19: </font></h2>
20:
21: <hr>
1.9 ! jason 22: <a href=stable.html>For OpenBSD patch branch information, please refer here.</a><br>
1.1 deraadt 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=errata.html>For 2.7 errata, please refer here</a>.<br>
29: <hr>
30:
31: <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.6.tar.gz>
32: You can also fetch a tar.gz file containing all the following patches</a>.
33: This file is updated once a day.
34:
35: <hr>
36:
37: <dl>
38: <a name=all></a>
39: <li><h3><font color=#e00000>All architectures</font></h3>
40: <ul>
1.7 deraadt 41: <a name=semconfig></a>
42: <li><font color=#009000><strong>024: SECURITY FIX: May 26, 2000</strong></font><br>
43: Kernel contained an undocumented system call used to lock semaphore operations
44: while they were being sampled by the ipcs(1) command. This locking could be
1.8 deraadt 45: used as a local denial of service attack which would block the exiting of
46: processes which had semaphore resources allocated. Processes not using
47: semaphores are not affected, so the actual effect is very minimal.<br>
1.7 deraadt 48: <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.6/common/024_sysv_sem.patch>
49: A jumbo patch exists which remedies this problem.</a>
50: <p>
1.4 kjell 51: <a name=ipf></a>
52: <li><font color=#009000><strong>023: SECURITY FIX: May 25, 2000</strong></font><br>
1.5 deraadt 53: A misuse of
54: <a href="http://www.openbsd.org/cgi-bin/man.cgi?query=ipf&sektion=8">ipf(8)</a>
1.4 kjell 55: <i>keep-state</i> rules can result in firewall rules being
1.5 deraadt 56: bypassed.
57: This patch also includes fixes for an unaligned timestamp issue,
1.4 kjell 58: and reliability fixes for ipmon and the in-kernel ftp proxy.<br>
59: <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.6/common/023_ipf.patch>
60: A jumbo patch exists</a>, which remedies this problem, and updates ipf
61: to version 3.3.16.
62: <p>
1.2 deraadt 63: <a name=xlockmore></a>
64: <li><font color=#009000><strong>022: SECURITY FIX: May 25, 2000</strong></font><br>
65: xlockmore has a localhost attack against it which allows recovery of the encrypted
66: hash of the root password. The damage to systems using DES passwords from this
67: attack is pretty heavy, but to systems with a well-chosen root password under
68: blowfish encoding
69: (see <a href="http://www.openbsd.org/cgi-bin/man.cgi?query=crypt&sektion=3">
70: crypt(3)</a>)
71: the impact is much reduced.<br>
72: (Aside: We do not consider this a localhost root hole in the default install,
73: since we have not seen a fast blowfish cracker yet ;-)<br>
1.3 deraadt 74: <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.6/common/022_xlockmore.patch>
1.6 deraadt 75: A source code patch exists, which remedies this problem. This is the 2nd patch designed to solve this problem.</a>
1.2 deraadt 76: <p>
1.1 deraadt 77: <a name=rzsz></a>
78: <li><font color=#009000><strong>021: RZSZ SNOOPING: Jan 31, 2000</strong></font><br>
79: The rzsz port was removed from the ports collection, as it collects and
80: sends user information to a designated email address, effectively spying on
81: you. <em>It is recommended that you remove this package if you installed
82: it</em>.
83: <p>
84: <a name=syslog></a>
85: <li><font color=#009000><strong>020: LIBRARY IMPROVEMENT: Jan 26, 2000</strong></font><br>
86: syslog(3) would not try to reopen the socket, thus, nightly newsyslog(8)
87: would cause syslogd(8) to not see new messages.
88: <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.6/common/020_syslog.patch>
89: A source code patch exists, which remedies this problem.</a>
90: <p>
91: <a name=nsphy></a>
92: <li><font color=#009000><strong>019: DRIVER IMPROVEMENT: Jan 20, 2000</strong></font><br>
93: Intel fxp cards with National Semiconductor PHYs (nsphy) have trouble
94: negotiating and maintaining 100Mb link integrity.<br>
95: <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.6/common/019_nsphy.patch>
96: A source code patch exists, which remedies this problem.</a>
97: <p>
98: <a name=procfs></a>
99: <li><font color=#009000><strong>018: SECURITY FIX: Jan 20, 2000</strong></font><br>
100: Systems running with procfs enabled and mounted are vulnerable
101: to having the stderr output of setuid processes directed onto
102: a pre-seeked descriptor onto the stack in their own procfs memory.<br>
103: Note that procfs is not mounted by default in OpenBSD.<br>
104: <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.6/common/018_procfs.patch>
105: A source code patch exists, which remedies this problem.</a>
106: <p>
107: <a name=aty2k></a>
108: <li><font color=#009000><strong>015: Y2K FIX: Jan 9, 2000</strong></font><br>
109: The at(1) command was unable to parse some kinds of dates.<br>
110: <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.6/common/015_aty2k.patch>
111: A source code patch exists, which remedies this problem.</a>
112: <p>
113: <a name=addusery2k></a>
114: <li><font color=#009000><strong>013: Y2K FIX: Jan 3, 2000</strong></font><br>
115: A minor problem in the logging support for the adduser(8) command.<br>
116: <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.6/common/013_addusery2k.patch>
117: A source code patch exists, which remedies this problem.</a>
118: <p>
119: <a name=3c900b></a>
120: <li><font color=#009000><strong>012: DRIVER IMPROVEMENT: Jan 3, 2000</strong></font><br>
121: The 3C900B-TPO fails to select the correct media type (it never sees or
122: sends packets).<br>
123: <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.6/common/012_3c900b.patch>
124: A source code patch exists, which remedies this problem.</a>
125: <p>
126: <a name=poll></a>
127: <li><font color=#009000><strong>011: SECURITY FIX: Dec 4, 1999</strong></font><br>
128: Various bugs in poll(2) may cause a kernel crash.<br>
129: <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.6/common/011_poll.patch>
130: A source code patch exists, which remedies this problem.</a>
131: <p>
132: <a name=sendmail></a>
133: <li><font color=#009000><strong>010: SECURITY FIX: Dec 4, 1999</strong></font><br>
134: Sendmail had a race in aliases file handling, which this patch fixes.<br>
135: <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.6/common/010_sendmail.patch>
136: A source code patch exists, which remedies this problem.</a>
137: <p>
138: <a name=atapijumbo></a>
139: <li><font color=#009000><strong>009: DRIVER IMPROVEMENTS: Dec 4, 1999</strong></font><br>
140: Various improvements have been made to the IDE/ATAPI subsystem since
141: the 2.6 release shipped.<br>
142: Some of these improvements make some recalcitrant devices work much better.
143: <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.6/common/009_atapi.patch><br>
144: Revision 1 of this jumbo source code patch exists.</a><br>
145: <p>
146: <a name=sslUSA></a>
147: <li><font color=#009000><strong>016: SECURITY FIX: Dec 2, 1999</strong></font><br>
148: A buffer overflow in the RSAREF code included in the
149: USA version of the libssl package (called <strong>sslUSA</strong>, is
150: possibly exploitable in isakmpd if SSL/RSA features
151: are enabled or used.<br>
152: <a href=http://www.openssh.com>OpenSSH</a> and httpd (with -DSSL) are not
153: vulnerable.<br>
154: <strong>NOTE: International users using the ssl26 package are not affected.</strong>
155: <p>
156: To check what package you are using, use
157: <pre>
158: <b>#</b> pkg_info sslUSA26
159: </pre>
160: The patched library says:<br>
161: "ssl26.1 USA-only non-commercial crypto libs incl. SSL & RSA"
162: <p>
163: Non-commercial USA users who installed the ssl package before December 3
164: should upgrade their <strong>sslUSA26</strong> package using:<br>
165: <pre>
166: <b>#</b> pkg_delete sslUSA26
167: <b>#</b> pkg_add -v sslUSA26.tar.gz
168: </pre>
169: Using the new <strong>sslUSA26.tar.gz</strong> files which have been placed
170: on the FTP mirrors.<br>
171: <a href=advisories/sslUSA>For more information, see the advisory</a>.<br>
172: <strong>NOTE: this problem turned out to not be unexploitable in OpenSSH.</strong>
173: <p>
174: <a name=fortran></a>
175: <li><font color=#009000><strong>017: FUNCTIONALITY ADDITION: Nov 14, 1999</strong></font><br>
176: Fortran doesn't work right. The file /usr/include/g2c.h is missing in the
177: release.<br>
178: <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.6/common/008_fortran.patch>
179: A source code patch exists which remedies this problem.</a><br>
180: The patch fixes the source tree and describes how to properly add
181: <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.6/common/g2c.h>
182: the include file</a> to your system.
183: <p>
184: <a name=sshjumbo></a>
185: <li><font color=#009000><strong>005: FUNCTIONALITY ADDITION: Nov 11, 1999</strong></font><br>
186: Various OpenSSH improvements have been made since the 2.6 release shipped.<br>
187: To resolve the various (non-security related) features which users may want,
188: we are making a jumbo patch available. <strong>This is now at VERSION FOUR.</strong><br>
189: <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.6/common/005_sshjumbo.patch>
190: Revision 4 of this jumbo source code patch exists.</a><br>
191: <strong>NOTE: /etc/sshd_config and /etc/ssh_config may need changes.</strong>
192: <p>
193: <a name=m4></a>
194: <li><font color=#009000><strong>003: FUNCTIONALITY FIX: Nov 10, 1999</strong></font><br>
195: m4 is quite broken in the 2.6 release.<br>
196: <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.6/common/003_m4.patch>
197: The 3rd version of the source code patch exists, which remedies this problem.</a>
198: <p>
199: <a name=ifmedia></a>
200: <li><font color=#009000><strong>002: SECURITY FIX: Nov 9, 1999</strong></font><br>
201: Any user can change interface media configurations.<br>
202: <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.6/common/002_ifmedia.patch>
203: A source code patch exists which remedies this problem.</a>
204: <p>
205: <a name=newsyslog></a>
206: <li><font color=#009000><strong>001: RELIABILITY FIX: Nov 8, 1999</strong></font><br>
207: A race condition in newsyslog(8) can cause errors in log file rotation.<br>
208: <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.6/common/001_newsyslog.patch>
209: A source code patch exists which remedies this problem.</a>
210: <p>
211: </ul>
212: <p>
213: <a name=i386></a>
214: <li><h3><font color=#e00000>i386</font></h3>
215: <ul>
216: <li>No problems identified yet.
217: </ul>
218: <p>
219: <a name=mac68k></a>
220: <li><h3><font color=#e00000>mac68k</font></h3>
221: <ul>
222: <a name=m68k_locore></a>
223: <a name=mac68k_locore></a>
224: <li><font color=#009000><strong>007: RELIABILITY FIX: Nov 12, 1999</strong></font><br>
225: All m68k kernels can possibly be crashed by a user.<br>
226: <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.6/m68k/007_locore.patch>
227: A source code patch exists which remedies this problem.</a>
228: <p>
229: </ul>
230: <p>
231: <a name=sparc></a>
232: <li><h3><font color=#e00000>sparc</font></h3>
233: <ul>
234: <a name=eepromy2k></a>
235: <li><font color=#009000><strong>014: Y2K FIX: Jan 3, 2000</strong></font><br>
236: A minor problem; the sparc eeprom(8) command is not Y2K compliant.<br>
237: <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.6/sparc/014_eepromy2k.patch>
238: Revision 2 of the source code patch exists, which remedies this problem.</a>
239: <p>
240: <a name=sparc_locore></a>
241: <li><font color=#009000><strong>004: RELIABILITY FIX: Nov 12, 1999</strong></font><br>
242: The sparc kernel can be crashed by a user.<br>
243: <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.6/sparc/004_locore.patch>
244: A source code patch exists which remedies this problem.</a>
245: <p>
246: </ul>
247: <p>
248: <a name=amiga></a>
249: <li><h3><font color=#e00000>amiga</font></h3>
250: <ul>
251: <a name=amiga_locore></a>
252: <li><font color=#009000><strong>007: RELIABILITY FIX: Nov 12, 1999</strong></font><br>
253: All m68k kernels can possibly be crashed by a user.<br>
254: <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.6/m68k/007_locore.patch>
255: A source code patch exists which remedies this problem.</a>
256: <p>
257: </ul>
258: <p>
259: <a name=pmax></a>
260: <li><h3><font color=#e00000>pmax</font></h3>
261: <ul>
262: <li>No problems identified yet.
263: </ul>
264: <p>
265: <a name=arc></a>
266: <li><h3><font color=#e00000>arc</font></h3>
267: <ul>
268: <li>No problems identified yet.
269: </ul>
270: <p>
271: <a name=alpha></a>
272: <li><h3><font color=#e00000>alpha</font></h3>
273: <ul>
274: <a name=alpha_locore></a>
275: <li><font color=#009000><strong>006: RELIABILITY FIX: Nov 13, 1999</strong></font><br>
276: The alpha kernel can possibly be crashed by a user.<br>
277: <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.6/alpha/006_locore.patch>
278: A source code patch exists which remedies this problem.</a>
279: <p>
280: </ul>
281: <p>
282: <a name=hp300></a>
283: <li><h3><font color=#e00000>hp300</font></h3>
284: <ul>
285: <a name=hp300_locore></a>
286: <li><font color=#009000><strong>007: RELIABILITY FIX: Nov 12, 1999</strong></font><br>
287: All m68k kernels can possibly be crashed by a user.<br>
288: <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.6/m68k/007_locore.patch>
289: A source code patch exists which remedies this problem.</a>
290: <p>
291: </ul>
292: <p>
293: <a name=mvme68k></a>
294: <li><h3><font color=#e00000>mvme68k</font></h3>
295: <ul>
296: <a name=mvme68k_locore></a>
297: <li><font color=#009000><strong>007: RELIABILITY FIX: Nov 12, 1999</strong></font><br>
298: All m68k kernels can possibly be crashed by a user.<br>
299: <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.6/m68k/007_locore.patch>
300: A source code patch exists which remedies this problem.</a>
301: <p>
302: </ul>
303: <p>
304: <a name=powerpc></a>
305: <li><h3><font color=#e00000>powerpc</font></h3>
306: <ul>
307: <li>No problems identified yet.
308: </ul>
309:
310: </dl>
311: <br>
312:
313: <hr>
1.9 ! jason 314: <a href=stable.html>For OpenBSD patch branch information, please refer here.</a><br>
1.1 deraadt 315: <a href=errata21.html>For 2.1 errata, please refer here</a>.<br>
316: <a href=errata22.html>For 2.2 errata, please refer here</a>.<br>
317: <a href=errata23.html>For 2.3 errata, please refer here</a>.<br>
318: <a href=errata24.html>For 2.4 errata, please refer here</a>.<br>
319: <a href=errata25.html>For 2.5 errata, please refer here</a>.<br>
320: <a href=errata.html>For 2.7 errata, please refer here</a>.<br>
321: <hr>
322:
323: <a href=index.html><img height=24 width=24 src=back.gif border=0 alt=OpenBSD></a>
324: <a href=mailto:www@openbsd.org>www@openbsd.org</a>
1.9 ! jason 325: <br><small>$OpenBSD: errata26.html,v 1.8 2000/05/27 00:58:55 deraadt Exp $</small>
1.1 deraadt 326:
327: </body>
328: </html>