This is the OpenBSD 2.2 release errata & patch list:

• All architectures

  • SECURITY FIX
    If the sysctl variable net.inet.ip.forwarding is enabled (value 1), but the variable net.inet.ip.sourceroute is disabled (value 0), the kernel will block source routed packets from going through, but will still accept source routing packets destined for itself. Our fix changes the net.inet.ip.sourceroute variable semantics to mean that all block all source routed packets should be blocked completely. A kernel patch is provided.

  • SECURITY FIX
    A combination localhost+remote host security problem exists if a local user running a setuid binary causes a non-existant root .rhosts file to be created via a symbolic link with a specific kind of corefile, and then subsequently uses rsh/rlogin to enter the machine from remote. A similar exploit might also be possible using sshd which lacks any code for checking for deviations from the expected format in the .rhosts or .shosts files, but we have not confirmed this yet. The following two fixes are recommended:
    • (1) A kernel patch which adds a new sysctl option which permits the administrator to decide whether setuid corefiles should be written or not.

    • (2) Replaces the ruserok() function in libc with a much more paranoid version which can detect these bogus looking .rhosts files better. If the previous patch is used to stop setuid coredumps, then this patch is not as important.

    This problem is fixed much better in OpenBSD-current, where the kernel's symbolic link handling has been improved such that coredumping will not create a file on the other side of a symbolic link. Such a patch is not possible for the 4.4lite1 VFS layer in the OpenBSD 2.2 kernel.

  • SECURITY FIX
    If you rely on the system securelevels as described in init(8), you will want this fix. A bug in the vm system permits a file descriptor opened read-only on a device, to later on be mmap(2)'d read-write, and then modified. This does not result in a security hole by itself, but it does violate the safety semantics which securelevels are supposed to provide. A kernel patch is available which corrects this behaviour.

  • BUILD PROCESS FIX
    Building an object tree from a read-only source tree (such as off a CDROM) may fail under certain circumstances (e.g. when creating a symlink on sparc whose target name is exactly 33 characters). As a workaround you have to either provide the source tree read/write, or install a newer version of /usr/bin/readlink. A replacement source file exists.

• i386

  • RELIABILITY FIX
    The Intel P5 F00F bug was discovered after the CDR's had already been sent to the manufacturer. This problem permits any user who has an account to lock your machine up using a 4-line program. The problem only affects Intel P5 processors (the i386, i486, P-Pro, and P-II are not vulnerable, nor are processors by other manufacturers). A kernel source-code patch is available.

  • FUNCTIONALITY FIX
    Some Linux binaries will execute in SVR4 emulation mode, which is definately a problem for people who need Linux emulation to work correctly. To solve this mis-identification problem, a patch file is provided.

  • RELIABILITY FIX
    APM can crash on machines without it. A kernel source-code patch is available.

  • INSTALLATION PROCESS FLAW
    A few people are running into this problem, particularily if they had some other *BSD operating system on their machine before trying OpenBSD: if after installation onto an IDE-based machine, the kernel fails to mount the root partition because it thinks that it should be opening sd0 (0x400), this means you have incorrectly setup your disklabel for the IDE drive -- the disklabel is indicating that the drive is SCSI. To repair this, use the floppy to run "disklabel -E wd0", then using the "edit" command ensure the type field is set to "ST506".

• mac68k

  • NEW SOFTWARE
    Unfortunately, X11 binaries for the mac68k did not manage to make it onto the CDROM. However, X11 for the mac68k is immediately available from ftp://ftp.OpenBSD.org/pub/OpenBSD/2.2/mac68k/X11/X11R6.tar.gz. Please be sure to read the README file also in that directory for instructions on installing and setting up X.

  • INSTALLATION PROCESS FLAW
    As shipped on the CDROM, both the generic kernel and the genericsbc kernel extract themselves into the wrong place in the filesystem. Both should extract a kernel named /bsd, but they extract the kernel into /usr/src/sys/arch/mac68k/compile instead.

    This has been fixed on the ftp release of OpenbSD 2.2, and fresh kernels are available from ftp://ftp.OpenBSD.ORG/pub/OpenBSD/2.2/mac68k/. If at all possible, installing these kernels is recommended.

    A number of possible workarounds exist if you don't have easy access to ftp the updated kernels. The simplest of these is to use a MacOS program to uncompress and untar the kernel aad use the Installer's mini-shell to "cpin" the kernel. Alternately, you could install the kernel with the Installer and use the mini-shell to move the binary from /usr/src/... to /bsd.

• sparc

  • RELIABILITY FIX
    Older 4/xxx systems (particularily the 4/300's) cannot boot with the 2.2 kernel due to bugs in the scsi device driver. A kernel source patch is available. Replacement kernels are available for: bsd, bsd.scsi3, and a replacement for bsd.rd is coming soon.

  • RELIABILITY FIX
    SPARCstation 4 and 5 (Microsparc 2) users may see kernel panics when using a custom kernel configured for option sun4m only. A workaround (kernel source patch) is available. Apply the patch and then re-build your kernel.

• amiga

  • FUNCTIONALITY FIX
    Missing Xamiga manual pages. Get this package and execute, as root:
    

    # pkg_add Xamiga-manual.tgz

    The MD5 checksum of this package is:
    MD5 (Xamiga-manual.tgz) = 2362a7857264b9d17f65cca258b42031

  • FUNCTIONALITY FIX
    The Ariadne ethernet support was broken, there will be both binary and source level fixes available shortly. If you are in a hurry mail Niklas for a test kernel.

• pmax

  • FUNCTIONALITY FIX
    There is a Year-1998 problem in the time-setting code (which causes the date and time to be set incorrectly after a reboot in 1998). A source code patch file is available plus replacement installation kernels for the 2.2 release at bsd.NFS, bsd, bsd.rz0.

  • FUNCTIONALITY FIX
    X11 support for the 3min and 3maxplus machines was broken due to a kernel bug. A source code patch is available.

  • SECURITY FIX
    A security problem in the shared library linker ld.so requires that you replace it with a new binary. The replacement binary is here.

• arc

  • SECURITY FIX
    A security problem in the shared library linker ld.so requires that you replace it with a new binary. The replacement binary is here.

• alpha

  • No problems identified yet.

• hp300

  • No problems identified yet.

• mvme68k

  • No problems identified yet.

This is the OpenBSD 2.1 release errata & patch list:

• All architectures

  • One of the install scripts has a flaw that makes the CD-ROM mount fail when using the CD-ROM as the install source media. To workaround this use the following sequence of commands before starting the install script. This must be done each time the install kernel is booted if the install script is to be run and the CD-ROM is the media to install from. Do the following at the shell prompt:

    # ed install.sub
    /{_filesystem/s//{_fstype/
    wq
    #
    

    For architectures where the install scripts start automatically (like amiga), you need to abort it at the (I)nstall or (U)pdate prompt by pressing Ctrl-C before doing the above command. After that you can restart the install by:

    # install
    

  
  

• Alpha

  • CD2 does not boot on the alpha, as had been planned. Instead, you must use the floppy install method. This is not significantly harder..
  
  

• i386

  • Some rarer PC BIOS's do not like the hardrive bootblocks when used as a MBR. The symptom is that the BIOS says "READ ERROR" when booting, but everything suggests it should work fine. In those cases, it is sufficient to install OS-BS or some other primary bootloader as the main MBR, then install OpenBSD in a partition all by itself starting at a non-zero offset. For instance, start OpenBSD at next track boundary or so.
  • The i386/X11/SUMS.md5 file contains 4 incorrect MD5 checksums. These have been corrected on the ftp mirrors. The correct lines are:
    MD5 (X33doc.tgz) = 6aa0be7987f9a3cf32a63b5ea9a83b39
    MD5 (X33html.tgz) = 6ba39d41aef7c75c35a0533275c6f8c0
    MD5 (X33ps.tgz) = ea49fc1b12c17fc16ece7d0e4ad4ee06
    MD5 (RELNOTES) = 689fda20596a4eb82f86ded51efb01f4
    
  • A lot of people with IDE disk drives fail to read the INSTALL.i386 document, and hence end up with geometry translation problems. Read the document, please.
  
  

• Amiga

  • The amiga install has a flaw wrt Tseng based graphic cards: when entering multiuser mode the console won't get a login prompt. This is due to a problem in the shipped /dev/MAKEDEV script. To fix, enter single user mode and do:

    # cd /dev
    # sh MAKEDEV ttye6
    

• Sparc

  • The sparc X11R6.3 xdm-config files reference /usr/X11R6.3/... This is due to X11R6.3's default config file contents. To fix, su and type:

    # cd /usr
    # ln -s X11R6 X11R6.3
    

  • The sparc "single floppy install disk" has a problem when you specify "dumb" in response to the terminal type query. As a work-around first specify an invalid terminal such as "bogus" and when prompted again for a terminal type, enter "dumb" and it will work correctly.
  • When netbooting an older sparc system such as a Sun4 or Sun4c, the boot may hang up at the end of the tftp transfer of the bootstrap due to the tftp transfer working in 512-byte blocks. If this occurs create a "padded" version of the bootstrap (boot or zboot) as follows:

    # cd /tftpboot
    # dd if=boot of=newboot obs=512 conv=osync
    # mv newboot boot
    

  • The sparc install script has two flaws that make the kernel copy and the bootblock install fail. The kernel copy only fails then installing from CD-ROM. To workaround this use the following sequence of commands before starting the install script. This must be done each time the install kernel is booted if the install script is to be run and the CD-ROM is the media to install from. Do the following at the shell prompt: if you install from CD-ROM do the following:

    # ed install.md 
    /\/bsd/s//\/mnt2\/2.1\/sparc\/bsd/ 
    wq 
    #
    

    ... or if you plan to use the bsd.scsi3 kernel you should use instead:

    # ed install.md 
    /\/bsd/s//\/mnt2\/2.1\/sparc\/bsd.scsi3/ 
    wq 
    #
    

    The following one you'll have to do always (not only then installing from from CD-ROM)

    # ed /usr/mdec/binstall 
    /getopt/,/getopt/+4d 
    wq 
    #
    

• Pmax

  • When using the X11R6 binaries from the 2.1 release you will get errors like:

    # mkfontdir
    mkfontdir: undefined symbol: 'astpending' 12
    Segmentation fault (core dumped)
    

    this is due to a little problem affecting the compatibility between the OpenBSD/arc port (on which the X11R6 clients were build) and OpenBSD/pmax. You can work around this problem by using the arc version of the shared libc instead of the pmax one. You may get a copy of the OpenBSD/arc 2.1 libc.so.16.1 from here . Simply download it and do the following:

    # cd /usr/lib
    # mv libc.so.16.1 original_libc.so.16.1
    # cp /where_you_have_downloaded_it_to/libc.so.16.1 .
    # chown root.bin libc.so.16.1
    # chmod 444 libc.so.16.1
    

    Please be careful while doing this - because the libc is a very sensitive part of the system. You can remove the original_libc.so.16.1 after the next reboot if everything is working fine.

• Mac68k

  • The installer generates incorrect /etc/fstab files causing messages such as "file system read-only" on bootup. To correct, boot to single-user mode (by clicking that checkbox in the Booter's Booting:Options dialog) and do the following:

    # mount /dev/sd0a /
    # ed /etc/fstab
    1,$s/ ufs / ffs /
    1,$s/ ro / rw /
    w
    q
    

    Alternately, simply invoke vi or another editor and change the root filesystem to be of type ffs rather than ufs and be rw (read-write) rather than ro (read-only). In either case, you'll need to reboot the system afterwards. Make this correction as soon as possible after installing the system. The installer should not have specified the filesystem as the old "ufs" type; the "ffs" type is more correct.
  • The installer forgets to install the kernel onto the filesystem. This is because the installer expects all packages including the kernel to be tar'ed and gzip'ed. The kernel was not shipped that way. Therefore, you must make this correction before attempting to boot the system. To correct, use the Installer mini-shell and do the following:

    > cpin :[internal-macos-path]:bsd-generic bsd
    

    This should place the kernel as /bsd on the filesystem. You should replace the above string with the colon-delimited path from your desktop to wherever you have placed the kernel. If possible, it is easiest to drag the kernel into the same folder as the Installer, so you can simply issue a command without leading colon(s) like:

    > cpin bsd-generic bsd
    

    Good luck.