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