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