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