=================================================================== RCS file: /cvsrepo/anoncvs/cvs/www/errata26.html,v retrieving revision 1.85 retrieving revision 1.86 diff -c -r1.85 -r1.86 *** www/errata26.html 2019/05/27 22:55:19 1.85 --- www/errata26.html 2019/05/28 16:32:41 1.86 *************** *** 84,173 ****

! 024: SECURITY FIX: May 26, 2000 All architectures
! Kernel contained an undocumented system call used to lock semaphore operations ! while they were being sampled by the ipcs(1) command. This locking could be ! used as a local denial of service attack which would block the exiting of ! processes which had semaphore resources allocated. Processes not using ! semaphores are not affected, so the actual effect is very minimal.
! A source code patch exists which remedies this problem.
!
! 023: SECURITY FIX: May 25, 2000 All architectures
! A misuse of ipf(8) ! keep-state rules can result in firewall rules being ! bypassed. ! This patch also includes fixes for an unaligned timestamp issue, ! and reliability fixes for ipmon and the in-kernel ftp proxy.
! A source code patch exists which remedies this problem. - It updates ipf to version 3.3.16.
!
! 022: SECURITY FIX: May 25, 2000 All architectures
! xlockmore has a localhost attack against it which allows recovery of the encrypted ! hash of the root password. The damage to systems using DES passwords from this ! attack is pretty heavy, but to systems with a well-chosen root password under ! blowfish encoding ! (see ! crypt(3)) ! the impact is much reduced.
! (Aside: We do not consider this a localhost root hole in the default install, ! since we have not seen a fast blowfish cracker yet ;-)
! A source code patch exists which remedies this problem. ! This is the 2nd patch designed to solve this problem.
!
! 021: RZSZ SNOOPING: Jan 31, 2000 All architectures
! The rzsz port was removed from the ports collection, as it collects and ! sends user information to a designated email address, effectively spying on ! you. It is recommended that you remove this package if you installed ! it.
!
! 020: LIBRARY IMPROVEMENT: Jan 26, 2000 All architectures
! syslog(3) would not try to reopen the socket, thus, nightly newsyslog(8) ! would cause syslogd(8) to not see new messages. ! A source code patch exists which remedies this problem.
!
! 019: DRIVER IMPROVEMENT: Jan 20, 2000 All architectures
! Intel fxp cards with National Semiconductor PHYs (nsphy) have trouble ! negotiating and maintaining 100Mb link integrity.
! A source code patch exists which remedies this problem.
!
! 018: SECURITY FIX: Jan 20, 2000 All architectures
! Systems running with procfs enabled and mounted are vulnerable ! to having the stderr output of setuid processes directed onto ! a pre-seeked descriptor onto the stack in their own procfs memory.
! Note that procfs is not mounted by default in OpenBSD.
! A source code patch exists which remedies this problem.
!
! 017: FUNCTIONALITY ADDITION: Nov 14, 1999 All architectures
! Fortran doesn't work right. The file /usr/include/g2c.h is missing in the ! release.
! A source code patch exists which remedies this problem. - The patch fixes the source tree and describes how to properly add - - the include file to your system.
016: SECURITY FIX: Dec 2, 1999 All architectures
--- 84,209 ----
- ! 001: RELIABILITY FIX: Nov 8, 1999 All architectures
  ! A race condition in newsyslog(8) can cause errors in log file rotation.
  ! A source code patch exists which remedies this problem.
  ! !
- ! 002: SECURITY FIX: Nov 9, 1999 All architectures
  ! Any user can change interface media configurations.
  ! A source code patch exists which remedies this problem.
  ! !
- ! 003: FUNCTIONALITY FIX: Nov 10, 1999 All architectures
  ! m4 is quite broken in the 2.6 release.
  ! A source code patch exists which remedies this problem. ! This is the 3rd revision of the patch.
  ! !
- ! 004: RELIABILITY FIX: Nov 12, 1999 ! sparc only
  ! The sparc kernel can be crashed by a user.
  ! ! A source code patch exists which remedies this problem. !
  ! !
- ! 005: FUNCTIONALITY ADDITION: Nov 11, 1999 All architectures
  ! Various OpenSSH improvements have been made since the 2.6 release shipped.
  ! To resolve the various (non-security related) features which users may want, ! we are making a jumbo patch available. This is now at VERSION FOUR.
  ! ! Revision 4 of this jumbo source code patch exists.
  ! NOTE: /etc/sshd_config and /etc/ssh_config may need changes.
  ! !
- ! 006: RELIABILITY FIX: Nov 13, 1999 ! alpha only
  ! The alpha kernel can possibly be crashed by a user.
  ! ! A source code patch exists which remedies this problem. !
  ! !
- ! 007: RELIABILITY FIX: Nov 12, 1999 ! m68k architectures
  ! All m68k kernels can possibly be crashed by a user.
  ! ! A source code patch exists which remedies this problem. !
  ! !
- ! 009: DRIVER IMPROVEMENTS: Dec 4, 1999 All architectures
  ! Various improvements have been made to the IDE/ATAPI subsystem since ! the 2.6 release shipped.
  ! Some of these improvements make some recalcitrant devices work much better. !
  ! Revision 1 of this jumbo source code patch exists.
  !
  ! !
- ! 010: SECURITY FIX: Dec 4, 1999 ! All architectures
  ! Sendmail had a race in aliases file handling, which this patch fixes.
  ! A source code patch exists which remedies this problem.
  ! !
- ! 011: SECURITY FIX: Dec 4, 1999 All architectures
  ! Various bugs in poll(2) may cause a kernel crash.
  ! A source code patch exists which remedies this problem.
  ! !
- ! 012: DRIVER IMPROVEMENT: Jan 3, 2000 All architectures
  ! The 3C900B-TPO fails to select the correct media type (it never sees or ! sends packets).
  ! A source code patch exists which remedies this problem.
  ! !
- ! 013: Y2K FIX: Jan 3, 2000 All architectures
  ! A minor problem in the logging support for the adduser(8) command.
  ! A source code patch exists which remedies this problem.
  + +
- + 014: Y2K FIX: Jan 3, 2000
  + A minor problem; the sparc eeprom(8) command is not Y2K compliant.
  + + A source code patch exists which remedies this problem. + This is the second revision of the patch. +
  + +
- + 015: Y2K FIX: Jan 9, 2000 + All architectures
  + The at(1) command was unable to parse some kinds of dates.
  + + A source code patch exists which remedies this problem. +
  +
- 016: SECURITY FIX: Dec 2, 1999 All architectures
  *************** *** 197,305 **** For more information, see the advisory.
  NOTE: this problem turned out to not be unexploitable in OpenSSH.
  !
- ! 015: Y2K FIX: Jan 9, 2000 All architectures
  ! The at(1) command was unable to parse some kinds of dates.
  ! A source code patch exists which remedies this problem.
  !
- ! 014: Y2K FIX: Jan 3, 2000
  ! A minor problem; the sparc eeprom(8) command is not Y2K compliant.
  ! ! A source code patch exists which remedies this problem. ! This is the second revision of the patch. !
  !
- ! 013: Y2K FIX: Jan 3, 2000 All architectures
  ! A minor problem in the logging support for the adduser(8) command.
  ! A source code patch exists which remedies this problem.
  !
- ! 012: DRIVER IMPROVEMENT: Jan 3, 2000 All architectures
  ! The 3C900B-TPO fails to select the correct media type (it never sees or ! sends packets).
  ! A source code patch exists which remedies this problem.
  !
- ! 011: SECURITY FIX: Dec 4, 1999 All architectures
  ! Various bugs in poll(2) may cause a kernel crash.
  ! A source code patch exists which remedies this problem.
  !
- ! 010: SECURITY FIX: Dec 4, 1999 All architectures
  ! Sendmail had a race in aliases file handling, which this patch fixes.
  ! ! A source code patch exists which remedies this problem.
  !
- ! 009: DRIVER IMPROVEMENTS: Dec 4, 1999 All architectures
  ! Various improvements have been made to the IDE/ATAPI subsystem since ! the 2.6 release shipped.
  ! Some of these improvements make some recalcitrant devices work much better. !
  ! Revision 1 of this jumbo source code patch exists.
  !
  !
- ! 007: RELIABILITY FIX: Nov 12, 1999 ! m68k architectures
  ! All m68k kernels can possibly be crashed by a user.
  ! A source code patch exists which remedies this problem.
  !
- ! 006: RELIABILITY FIX: Nov 13, 1999 ! alpha only
  ! The alpha kernel can possibly be crashed by a user.
  ! ! A source code patch exists which remedies this problem. !
  !
- ! 005: FUNCTIONALITY ADDITION: Nov 11, 1999 All architectures
  ! Various OpenSSH improvements have been made since the 2.6 release shipped.
  ! To resolve the various (non-security related) features which users may want, ! we are making a jumbo patch available. This is now at VERSION FOUR.
  ! ! Revision 4 of this jumbo source code patch exists.
  ! NOTE: /etc/sshd_config and /etc/ssh_config may need changes. !
  !
- ! 004: RELIABILITY FIX: Nov 12, 1999 ! sparc only
  ! The sparc kernel can be crashed by a user.
  ! A source code patch exists which remedies this problem.
  !
- ! 003: FUNCTIONALITY FIX: Nov 10, 1999 All architectures
  ! m4 is quite broken in the 2.6 release.
  ! ! A source code patch exists which remedies this problem. ! This is the 3rd revision of the patch. !
  !
- ! 002: SECURITY FIX: Nov 9, 1999 ! All architectures
  ! Any user can change interface media configurations.
  ! ! A source code patch exists which remedies this problem. !
  !
- ! 001: RELIABILITY FIX: Nov 8, 1999 ! All architectures
  ! A race condition in newsyslog(8) can cause errors in log file rotation.
  ! A source code patch exists which remedies this problem.
  --- 233,328 ---- For more information, see the advisory.
  NOTE: this problem turned out to not be unexploitable in OpenSSH.
  ! !
- ! 017: FUNCTIONALITY ADDITION: Nov 14, 1999 All architectures
  ! Fortran doesn't work right. The file /usr/include/g2c.h is missing in the ! release.
  ! A source code patch exists which remedies this problem. + The patch fixes the source tree and describes how to properly add + + the include file to your system.
  ! !
- ! 018: SECURITY FIX: Jan 20, 2000 All architectures
  ! Systems running with procfs enabled and mounted are vulnerable ! to having the stderr output of setuid processes directed onto ! a pre-seeked descriptor onto the stack in their own procfs memory.
  ! Note that procfs is not mounted by default in OpenBSD.
  ! A source code patch exists which remedies this problem.
  ! !
- ! 020: LIBRARY IMPROVEMENT: Jan 26, 2000 All architectures
  ! syslog(3) would not try to reopen the socket, thus, nightly newsyslog(8) ! would cause syslogd(8) to not see new messages. ! A source code patch exists which remedies this problem.
  ! !
- ! 019: DRIVER IMPROVEMENT: Jan 20, 2000 All architectures
  ! Intel fxp cards with National Semiconductor PHYs (nsphy) have trouble ! negotiating and maintaining 100Mb link integrity.
  ! A source code patch exists which remedies this problem.
  ! !
- ! 021: RZSZ SNOOPING: Jan 31, 2000 All architectures
  ! The rzsz port was removed from the ports collection, as it collects and ! sends user information to a designated email address, effectively spying on ! you. It is recommended that you remove this package if you installed ! it.
  ! !
- ! 022: SECURITY FIX: May 25, 2000 All architectures
  ! xlockmore has a localhost attack against it which allows recovery of the encrypted ! hash of the root password. The damage to systems using DES passwords from this ! attack is pretty heavy, but to systems with a well-chosen root password under ! blowfish encoding ! (see ! crypt(3)) ! the impact is much reduced.
  ! (Aside: We do not consider this a localhost root hole in the default install, ! since we have not seen a fast blowfish cracker yet ;-)
  ! A source code patch exists which remedies this problem. + This is the 2nd patch designed to solve this problem.
  ! !
- ! 023: SECURITY FIX: May 25, 2000 All architectures
  ! A misuse of ipf(8) ! keep-state rules can result in firewall rules being ! bypassed. ! This patch also includes fixes for an unaligned timestamp issue, ! and reliability fixes for ipmon and the in-kernel ftp proxy.
  ! A source code patch exists which remedies this problem. + It updates ipf to version 3.3.16.
  ! !
- ! 024: SECURITY FIX: May 26, 2000 All architectures
  ! Kernel contained an undocumented system call used to lock semaphore operations ! while they were being sampled by the ipcs(1) command. This locking could be ! used as a local denial of service attack which would block the exiting of ! processes which had semaphore resources allocated. Processes not using ! semaphores are not affected, so the actual effect is very minimal.
  ! A source code patch exists which remedies this problem.