Annotation of www/34.html, Revision 1.15
1.1 david 1: <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
2: <html>
3: <head>
4: <title>OpenBSD 3.4 Release</title>
5: <link rev=made href="mailto:www@openbsd.org">
6: <meta name="resource-type" content="document">
7: <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
8: <meta name="description" content="OpenBSD 3.4">
9: <meta name="keywords" content="openbsd,main">
10: <meta name="distribution" content="global">
11: <meta name="copyright" content="This document copyright 2003 by OpenBSD.">
12: </head>
13:
14: <body bgcolor="#ffffff" text="#000000" link="#24248E">
15:
16: <a href="index.html">
17: <img alt="[OpenBSD]" height="30" width="141" hspace="24" src="images/smalltitle.gif" border="0"></a>
18: <hr>
19:
20: <p>
21: <a href="images/Hood.gif">
22: <img align="left" width="255" height="343" hspace="24"
23: src="images/Hood.gif" alt="OpenBSD 3.4 logo"></a>
24: <h2><font color="#0000e0">The OpenBSD 3.4 Release:</font></h2>
25: <p>
26:
27: Released Nov 1, 2003<br>
28: Copyright 1997-2003, Theo de Raadt.<br>
29: <font color="#e00000">ISBN 0-9731791-2-0</font>
30: <p>
31:
32: <a href="#new">What's New</a><br>
33: <a href="#install">How to install</a><br>
34: <a href="#ports">How to use the ports tree</a><br>
35: <a href="orders.html">Ordering a CD set</a><br>
36:
37: <p>
38: <h3><font color="#0000e0">
39: To get the files for this release:
40: <ul>
41: <li>Order a CDROM from our <a href="orders.html">ordering system</a>.
42: <li>See the information on <a href="ftp.html">The FTP page</a> for
1.8 david 43: a list of mirror machines.
1.1 david 44: <li>Go to the <font color="#e00000">pub/OpenBSD/3.4/</font> directory on
1.8 david 45: one of the mirror sites.
1.1 david 46: <li>Briefly read the rest of this document.
47: <li>Have a look at <a href="errata.html">The 3.4 Errata page</a> for a list
1.8 david 48: of bugs and workarounds.
1.1 david 49: <li>See a <a href="plus.html">detailed log of changes</a> between the
1.8 david 50: 3.3 and 3.4 releases.
1.1 david 51: </ul>
52: </font></h3>
53: <br clear=all>
54: <br>
55: <p>
56:
57: <strong>Note:</strong> All applicable copyrights and credits can be found
58: in the applicable file sources found in the files src.tar.gz, sys.tar.gz,
59: XF4.tar.gz, or in the files fetched via ports.tar.gz. The distribution
60: files used to build packages from the ports.tar.gz file are not included on
61: the CDROM because of lack of space.
62: <p>
63:
64: <a name="new"></a>
65: <hr>
66: <p>
67: <h3><font color="#0000e0">What's New</font></h3>
68: <p>
69: This is a partial list of new features and systems included in OpenBSD 3.4.
70: For a comprehensive list, see the <a href="plus.html">changelog</a> leading
71: to 3.4.
72: <p>
73:
74: <ul>
75:
1.13 david 76: <li>The i386 architecture has been switched to the ELF executable format so
77: i386 upgrades are not possible for this release.
1.1 david 78: <p>
79:
1.6 tedu 80: <li>Further W^X improvements, including support for the i386 architecture.
81: Native i386 binaries have their executable segments rearranged to support
1.14 deraadt 82: isolating code from data, and the cpu CS limit is used to impose a best
83: effort limit on code execution.
1.1 david 84: <p>
85:
1.6 tedu 86: <li>ld.so on ELF platforms now loads libraries in a random order for
1.14 deraadt 87: greater resistance to attacks. The i386 architecture also maps libraries
88: somewhat randomized addresses. Together with W^X and ProPolice, these
89: changes increase the difficulty of successfully exploiting an application
90: error, such as a buffer overflow.
1.1 david 91: <p>
92:
93: <li>A static bounds checker has been added to the compiler to perform basic
1.4 avsm 94: checks on functions which accept buffers and sizes. The checker aims to
1.8 david 95: find common mistakes in the use of library functions such as
1.4 avsm 96: <a href="http://www.openbsd.org/cgi-bin/man.cgi?query=strlcpy">strlcpy(3)</a>
97: or <a href="http://www.openbsd.org/cgi-bin/man.cgi?query=sscanf">sscanf(3)</a>
98: without emitting any false positives. Running it over the source and ports
99: trees revealed over a hundred real bugs, which were fixed and submitted back
100: to the original authors where possible.
1.1 david 101: <p>
102:
1.6 tedu 103: <li>Privilege separation has been implemented for the syslog daemon, making
104: it much more robust against future errors. The child which listens to
105: network traffic now runs as a normal user and chroots itself, while the
106: parent process tracks the state of the child and performs privileged
107: operations on its behalf.
1.1 david 108: <p>
109:
110: <li>Many unsafe string functions have been removed from the kernel and userland
1.6 tedu 111: utilities. This audit is one of the most comprehensive OpenBSD has ever
112: done, with thousands of occurrences of
1.12 deraadt 113: <a href="http://www.openbsd.org/cgi-bin/man.cgi?query=strcpy">strcpy(3)</a>,
114: <a href="http://www.openbsd.org/cgi-bin/man.cgi?query=strcat">strcat(3)</a>,
115: <a href="http://www.openbsd.org/cgi-bin/man.cgi?query=sprintf">sprintf(3)</a>,
1.8 david 116: and
1.12 deraadt 117: <a href="http://www.openbsd.org/cgi-bin/man.cgi?query=vsprintf">vsprintf(3)</a>
1.4 avsm 118: being replaced with safer, bounded alternatives such as
1.12 deraadt 119: <a href="http://www.openbsd.org/cgi-bin/man.cgi?query=strlcpy">strlcpy(3)</a>,
120: <a href="http://www.openbsd.org/cgi-bin/man.cgi?query=strlcat">strlcat(3)</a>,
121: <a href="http://www.openbsd.org/cgi-bin/man.cgi?query=snprintf">snprintf(3)</a>,
122: <a href="http://www.openbsd.org/cgi-bin/man.cgi?query=vsnprintf">vsnprintf(3)</a>,
123: and
124: <a href="http://www.openbsd.org/cgi-bin/man.cgi?query=asprintf">asprintf(3)</a>.
1.1 david 125: <p>
126:
1.13 david 127: <li><a href="http://www.research.ibm.com/trl/projects/security/ssp/">
128: ProPolice</a> stack protection has been enabled in the kernel as well.
1.1 david 129: <p>
130:
1.15 ! david 131: <li>Privileged separation has been implemented in the X server. The privileged
! 132: child process is responsible for the operations that can't be done after the
! 133: main process has switched to a non-privileged user. This greatly reduces the
! 134: potential damage that could be caused by malicious X clients, in case of
! 135: bugs in the X server.
! 136: <p>
! 137:
1.1 david 138: <li>Manual pages have been greatly cleaned up and improved.
139: <p>
140:
1.8 david 141: <li>The ports tree now supports building programs under
142: <a href="http://www.openbsd.org/cgi-bin/man.cgi?query=systrace">
143: systrace(1)</a>, preventing the possibility of applications harming the
144: system at compile-time via trojaned configuration scripts or otherwise.
1.1 david 145: <p>
146:
1.3 jason 147: <li>More licenses fixes, including the removal of the advertising clause
1.6 tedu 148: for large parts of the source tree.
149: <p>
150:
1.11 deraadt 151: <li>Replacement of GNU diff/diff3, grep/egrep/fgrep/zgrep/zegrep/zfgrep,
152: and gzip/zcat/gunzip/gzcat/zcmp/zmore/zdiff/zforce/gzexe/znew
153: with BSD licensed equivalents.
1.6 tedu 154: <p>
155:
156: <li>Addition of read-only support for NTFS file systems.
157: <p>
158:
159: <li>Reliability improvements to layered file systems, enabling NULLFS to
160: work again.
161: <p>
162:
163: <li>Improvements to the linux emulator enabling more applications to run.
164: <p>
165:
1.13 david 166: <li>Legacy KerberosIV support has been removed, and the remaining KerberosV
167: codebase has been restructured for easier management.
1.3 jason 168: <p>
169:
1.13 david 170: <li>Over 2400 ports, 2200 pre-built packages.
1.1 david 171: <p>
172:
173: <li>A large number of bug fixes, changes, and optimizations to our packet filter
174: including:
175: <ul>
1.9 dhartmei 176: <li>packet tagging (e.g. filter on tags added by bridge based on MAC address)
1.10 frantzen 177: <li>stateful TCP normalization (prevent uptime calculation and NAT detection)
1.9 dhartmei 178: <li>passive OS detection (filter or redirect connections based on source OS)
179: <li>SYN proxy (protect servers against SYN flood attacks)
180: <li>adaptive state timeouts (prevent state table overflows under attack)
1.1 david 181: </ul>
182: <p>
183:
184: <li>The system includes the following major components from outside suppliers:
185: <ul>
1.7 david 186: <li>XFree86 4.3.0 (+ patches, and i386 contains 3.3.X servers also, thus
187: providing support for all chipsets)
1.1 david 188: <li>Gcc 2.95.3 (+ patches)
189: <li>Perl 5.8.0 (+ patches)
190: <li>Apache 1.3.28, mod_ssl 2.8.15, DSO support (+ patches)
191: <li>OpenSSL 0.9.7beta3 (+ patches)
192: <li>Groff 1.15
193: <li>Sendmail 8.12.9
194: <li>Bind 9.2.2 (+ patches)
1.5 avsm 195: <li>Lynx 2.8.4rel.1 with HTTPS and IPv6 support (+ patches)
1.1 david 196: <li>Sudo 1.6.7p5
197: <li>Ncurses 5.2
198: <li>Latest KAME IPv6
199: <li>Heimdal 0.6rc1 (+ patches)
200: <li>Arla-current
201: <li>OpenSSH 3.7
202: </ul>
203: <p>
204:
205: <p>
206: <li>Many improvements for security and reliability (look for the red
207: print in the <a href="plus.html">complete changelog</a>).
208: <p>
209: <li> and much more.
210:
211: </ul>
212:
213: <a name="install"></a>
214: <hr>
215: <p>
216: <h3><font color="#0000e0">How to install</font></h3>
217: <p>
218: Following this are the instructions which you would have on a piece of
219: paper if you had purchased a CDROM set instead of doing an alternate
220: form of install. The instructions for doing an ftp (or other style
221: of) install are very similar; the CDROM instructions are left intact
222: so that you can see how much easier it would have been if you had
223: purchased a CDROM instead.
224: <p>
225:
226: <hr>
227: Please refer to the following files on the three CDROMs or ftp mirror for
228: extensive details on how to install OpenBSD 3.4 on your machine:
229: <p>
230: <ul>
1.8 david 231: <li>CD1:3.4/i386/INSTALL.i386
1.1 david 232: <p>
1.8 david 233: <li>CD2:3.4/macppc/INSTALL.macppc
234: <li>CD2:3.4/vax/INSTALL.vax
1.1 david 235: <p>
1.8 david 236: <li>CD3:3.4/sparc/INSTALL.sparc
237: <li>CD3:3.4/sparc64/INSTALL.sparc64
1.1 david 238: <p>
1.8 david 239: <li>FTP:.../OpenBSD/3.4/alpha/INSTALL.alpha
240: <li>FTP:.../OpenBSD/3.4/hp300/INSTALL.hp300
241: <li>FTP:.../OpenBSD/3.4/hppa/INSTALL.hppa
242: <li>FTP:.../OpenBSD/3.4/mac68k/INSTALL.mac68k
243: <li>FTP:.../OpenBSD/3.4/mvme68k/INSTALL.mvme68k
1.1 david 244: </ul>
245: <hr>
246:
247: <p>
248: Quick installer information for people familiar with OpenBSD, and the
249: use of the "disklabel -E" command. If you are at all confused when
250: installing OpenBSD, read the relevant INSTALL.* file as listed above!
251: <p>
252:
253: <h3><font color="#e00000">OpenBSD/i386:</font></h3>
254: <ul>
255: Play with your BIOS options to enable booting from a CD. The OpenBSD/i386
256: release is on CD1. If your BIOS does not support booting from CD, you will need
257: to create a boot floppy to install from. To create a boot floppy write
258: <i>CD1:3.4/i386/floppy34.fs</i> to a floppy and boot via the floppy drive.
259:
260: <p>
261: Use <i>CD1:3.4/i386/floppyB34.fs</i> instead for greater scsi controller
262: support, or <i>CD1:3.4/i386/floppyC34.fs</i> for better laptop support.
263:
264: <p>
1.2 david 265: If you are planning on dual booting OpenBSD with another OS, you will need to
266: read the included INSTALL.i386 document.
1.1 david 267:
268: <p>
269: To make a boot floppy under MS-DOS, use the "rawrite" utility located
1.2 david 270: at <i>CD:/3.4/tools/rawrite.exe</i>. To make the boot floppy under a Unix OS,
271: use the <a href="http://www.openbsd.org/cgi-bin/man.cgi?query=
272: dd&sektion=1">dd(1)</a> utility. The following is an example usage of
273: <a href="http://www.openbsd.org/cgi-bin/man.cgi?query=dd&sektion=1">dd(1)
274: </a>, where the device could be "floppy", "rfd0c", or
275: "rfd0a".
1.1 david 276:
277: <ul><pre>
278: # <strong>dd if=<file> of=/dev/<device> bs=32k</strong>
279: </pre></ul>
280:
281: <p>
1.2 david 282: Make sure you use properly formatted perfect floppies with NO BAD BLOCKS or
283: your install will most likely fail. For more information on creating a boot
284: floppy and installing OpenBSD/i386 please refer to
285: <a href="faq/faq4.html#MkFlop">FAQ4.1</a>.
1.1 david 286: </ul>
287:
288: <p>
289: <h3><font color="#e00000">OpenBSD/macppc:</font></h3>
290: <ul>
291: Put the CD2 in your CDROM drive and poweron your machine while holding down the
292: <i>C</i> key until the display turns on and shows <i>OpenBSD/macppc boot</i>.
293:
294: <p>
295: Alternatively, at the Open Firmware prompt, enter <i>boot cd:,ofwboot
296: /3.4/macppc/bsd.rd</i>
297: </ul>
298:
299: <p>
300: <h3><font color="#e00000">OpenBSD/vax:</font></h3>
301: <ul>
302: Boot over the network via mopbooting as described in INSTALL.vax.
303: </ul>
304:
305: <p>
306: <h3><font color="#e00000">OpenBSD/sparc:</font></h3>
307: <ul>
1.2 david 308: The 3.4 release of OpenBSD/sparc is located on CD3. To boot off of this CD you
309: can use one of the two commands listed below, depending on the version of your
310: ROM.
1.1 david 311:
312: <ul><pre>
1.8 david 313: > <strong>boot cdrom 3.4/sparc/bsd.rd</strong>
1.1 david 314: or
1.8 david 315: > <strong>boot sd(0,6,0)3.4/sparc/bsd.rd</strong>
1.1 david 316: </pre></ul>
317:
318: <p>
319: If your sparc does not have a CD drive, you can alternatively boot from floppy.
1.2 david 320: To do so you need to write "CD3:3.4/sparc/floppy34.fs" to a floppy.
321: For more information see <a href="faq/faq4.html#MkFlop">FAQ4.1</a>. To boot from
322: the floppy use one of the two commands listed below, depending on the version of
323: your ROM.
1.1 david 324:
325: <ul><pre>
1.8 david 326: > <strong>boot floppy</strong>
1.1 david 327: or
1.8 david 328: > <strong>boot fd()</strong>
1.1 david 329: </pre></ul>
330:
331: <p>
1.2 david 332: Make sure you use a properly formatted floppy with NO BAD BLOCKS or your install
333: will most likely fail.
1.1 david 334:
335: <p>
336: If your sparc doesn't have a floppy drive nor a CD drive, you can either
337: setup a bootable tape, or install via network, as told in the
338: INSTALL.sparc file.
339: </ul>
340:
341: <p>
342: <h3><font color="#e00000">OpenBSD/sparc64:</font></h3>
343: <ul>
344: Put the CD3 in your CDROM drive and type <i>boot cdrom</i>.
345:
346: <p>
347: If this doesn't work, or if you don't have a CDROM drive, you can write
348: <i>CD3:3.4/sparc64/floppy34.fs</i> to a floppy and boot it with <i>boot
349: floppy</i>.<br>
1.2 david 350: Make sure you use a properly formatted floppy with NO BAD BLOCKS or your install
351: will most likely fail.
1.1 david 352:
353: <p>
354: You can also write <i>CD3:3.4/sparc64/miniroot34.fs</i> to the swap partition on
355: the disk and boot with <i>boot disk:b</i>.
356:
357: <p>
358: If nothing works, you can boot over the network as described in INSTALL.sparc64
359: </ul>
360:
361: <p>
362: <h3><font color="#e00000">OpenBSD/alpha:</font></h3>
363: <ul>
364: <p>Write <i>FTP:3.4/alpha/floppy34.fs</i> or
365: <i>FTP:3.4/alpha/floppyB34.fs</i> (depending on your machine) to a diskette and
366: enter <i>boot dva0</i>. Refer to INSTALL.alpha for more details.
367:
368: <p>
1.2 david 369: Make sure you use a properly formatted floppy with NO BAD BLOCKS or your install
370: will most likely fail.
1.1 david 371:
372: </ul>
373:
374: <p>
375: <h3><font color="#e00000">OpenBSD/hp300:</font></h3>
376: <ul>
377: <p>
378: Boot over the network by following the instructions in INSTALL.hp300.
379: </ul>
380:
381: <p>
382: <h3><font color="#e00000">OpenBSD/hppa:</font></h3>
383: <ul>
384: <p>
385: Boot over the network by following the instructions in INSTALL.hppa or the
386: <a href="hppa.html#netboot">hppa platform page</a>.
387: </ul>
388:
389: <p>
390: <h3><font color="#e00000">OpenBSD/mac68k:</font></h3>
391: <ul>
392: <p>
393: Boot MacOS as normal and partition your disk with the appropriate A/UX
394: configurations. Then, extract the Macside utilities from
395: <i>FTP:3.4/mac68k/utils</i> onto your hard disk. Run Mkfs to create your
396: filesystems on the A/UX partitions you just made. Then, use the
397: "BSD/Mac68k Installer" to copy all the sets in <i>FTP:3.4/mac68k/</i> onto your
398: partitions. Finally, you will be ready to configure the "BSD/Mac68k
399: Booter" with the location of your kernel and boot the system.
400: </ul>
401:
402: <p>
403: <h3><font color="#e00000">OpenBSD/mvme68k:</font></h3>
404: <ul>
405: <p>
406: You can create a bootable installation tape or boot over the network.<br>
407: The network boot requires a MVME68K BUG version that supports the <i>NIOT</i>
408: and <i>NBO</i> debugger commands. Follow the instructions in INSTALL.mvme68k
409: for more details.
410: </ul>
411:
412: <p>
413: <h3><font color="#e00000">Notes about the source code:</font></h3>
414: <ul>
415: src.tar.gz contains a source archive starting at /usr/src. This file
416: contains everything you need except for the kernel sources, which are
417: in a separate archive. To extract:
418: <p>
419: <ul><pre>
420: # <strong>mkdir -p /usr/src</strong>
421: # <strong>cd /usr/src</strong>
422: # <strong>tar xvfz /tmp/src.tar.gz</strong>
423: </pre></ul>
424: <p>
425: sys.tar.gz contains a source archive starting at /usr/src/sys.
426: This file contains all the kernel sources you need to rebuild kernels.
427: To extract:
428: <p>
429: <ul><pre>
430: # <strong>mkdir -p /usr/src/sys</strong>
431: # <strong>cd /usr/src</strong>
432: # <strong>tar xvfz /tmp/sys.tar.gz</strong>
433: </pre></ul>
434: <p>
435: Both of these trees are a regular CVS checkout. Using these trees it
436: is possible to get a head-start on using the anoncvs servers as
437: described <a href="anoncvs.html">here</a>.
438: Using these files
439: results in a much faster initial CVS update than you could expect from
440: a fresh checkout of the full OpenBSD source tree.
441: <p>
442: </ul>
443: <a name="ports"></a>
444: <hr>
445: <p>
446: <h3><font color="#0000e0">Ports Tree</font></h3>
447: <p>
448: A ports tree archive is also provided. To extract:
449: <p>
450: <ul><pre>
451: # <strong>cd /usr</strong>
452: # <strong>tar xvfz /tmp/ports.tar.gz</strong>
453: # <strong>cd ports</strong>
454: </pre></ul>
455: <p>
456: The <i>ports/</i> subdirectory is a checkout of the OpenBSD ports tree. Go
457: read the <a href="ports.html">ports</a> page
458: if you know nothing about ports
459: at this point. This text is not a manual of how to use ports.
460: Rather, it is a set of notes meant to kickstart the user on the
461: OpenBSD ports system.
462: <p>
463: Certainly, the OpenBSD ports system is not complete. It is doubtful it
464: will ever be. However, it is growing very fast and getting more stable.
465: Almost all ports provided with this release should build without problems
466: on most architectures (over 2400 packages build on i386, for instance).
467: <p>
468: The <i>ports/</i> directory represents a CVS (see the manpage for
469: <a href="http://www.openbsd.org/cgi-bin/man.cgi?query=cvs&apropos=0&sektion=1&manpath=OpenBSD+Current&arch=i386&format=html">
470: cvs(1)</a> if
471: you aren't familiar with CVS) checkout of our ports. As with our complete
472: source tree, our ports tree is available via anoncvs. So, in
473: order to keep current with it, you must make the <i>ports/</i> tree
474: available on a read-write medium and update the tree with a command
475: like:
476: <p>
477: <ul><pre>
478: # <strong>cd [portsdir]/; cvs -d anoncvsserver.openbsd.org:/cvs update -Pd -rOPENBSD_3_4</strong>
479: </pre></ul>
480: <p>
481: [Of course, you must replace the local directory and server name here
482: with the location of your ports collection and a nearby anoncvs
483: server.]
484: <p>
485: Note that most ports are available as packages through ftp. Updated
486: packages for the 3.4 release will be made available if problems arise.
487: <p>
488: If you're interested in seeing a port added, would like to help out, or just
489: would like to know more, the mailing list ports@openbsd.org is a good
490: place to know.
491: <p>
492:
493: <hr>
494: <a href="index.html"><img height="24" width="24" src="back.gif" border="0"
495: alt="OpenBSD"></a>
496: <a href="mailto:www@openbsd.org">www@openbsd.org</a>
497: <br><small>
1.15 ! david 498: $OpenBSD: 34.html,v 1.14 2003/09/04 19:15:21 deraadt Exp $
1.1 david 499: </small>
500:
501: </body>
502: </html>