===================================================================
RCS file: /cvsrepo/anoncvs/cvs/www/errata27.html,v
retrieving revision 1.85
retrieving revision 1.86
diff -c -r1.85 -r1.86
*** www/errata27.html	2016/08/15 02:22:06	1.85
--- www/errata27.html	2016/10/16 19:11:29	1.86
***************
*** 70,76 ****
  <br>
  <hr>
  
! <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/2.7.tar.gz">
  You can also fetch a tar.gz file containing all the following patches</a>.
  This file is updated once a day.
  <p>
--- 70,76 ----
  <br>
  <hr>
  
! <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.7.tar.gz">
  You can also fetch a tar.gz file containing all the following patches</a>.
  This file is updated once a day.
  <p>
***************
*** 97,103 ****
  application is mysql).  Additionally, if the HOME environment variable
  is not set, the current working directory is used; this patch disables
  the history file if HOME is not set.<br>
! <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/2.7/common/040_readline.patch">
  A source code patch exists which remedies this problem.</a>
  <p>
  <li id="sudo">
--- 97,103 ----
  application is mysql).  Additionally, if the HOME environment variable
  is not set, the current working directory is used; this patch disables
  the history file if HOME is not set.<br>
! <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.7/common/040_readline.patch">
  A source code patch exists which remedies this problem.</a>
  <p>
  <li id="sudo">
***************
*** 106,125 ****
  There is an exploitable heap corruption bug in
  <a href="http://man.openbsd.org/?query=sudo&amp;sektion=8">sudo</a>.
  <br>
! <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/2.7/common/038_named.patch">
  A source code patch exists which remedies this problem.</a>
  <p>
  <li id="ftpd">
  <font color="#009000"><strong>037: SECURITY FIX: Dec 4, 2000</strong></font>
  &nbsp; <i>All architectures</i><br>
  OpenBSD 2.7's ftpd contains a one-byte overflow in the replydirname() function.<br>
! <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/2.7/common/037_ftpd.patch">
  A source code patch exists which remedies this problem.</a>
  <p>
  <li id="qe">
  <font color="#009000"><strong>036: RELIABILITY FIX: Nov 17, 2000</strong></font><br>
  Configuring a qec+qe causes a NMI panic.<br>
! <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/2.7/sparc/036_qe.patch">
  A source code patch exists which remedies this problem.</a>
  <p>
  <li id="sshforwarding">
--- 106,125 ----
  There is an exploitable heap corruption bug in
  <a href="http://man.openbsd.org/?query=sudo&amp;sektion=8">sudo</a>.
  <br>
! <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.7/common/038_named.patch">
  A source code patch exists which remedies this problem.</a>
  <p>
  <li id="ftpd">
  <font color="#009000"><strong>037: SECURITY FIX: Dec 4, 2000</strong></font>
  &nbsp; <i>All architectures</i><br>
  OpenBSD 2.7's ftpd contains a one-byte overflow in the replydirname() function.<br>
! <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.7/common/037_ftpd.patch">
  A source code patch exists which remedies this problem.</a>
  <p>
  <li id="qe">
  <font color="#009000"><strong>036: RELIABILITY FIX: Nov 17, 2000</strong></font><br>
  Configuring a qec+qe causes a NMI panic.<br>
! <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.7/sparc/036_qe.patch">
  A source code patch exists which remedies this problem.</a>
  <p>
  <li id="sshforwarding">
***************
*** 127,147 ****
  &nbsp; <i>All architectures</i><br>
  Hostile servers can force OpenSSH clients to do agent or X11 forwarding.
  This problem is fixed as of OpenSSH 2.3.0.<br>
! <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/2.7/common/035_sshforwarding.patch">
  A source code patch exists which remedies this problem.</a>
  <p>
  <li id="zsconsole">
  <font color="#009000"><strong>034: RELIABILITY FIX: Nov 10, 2000</strong></font><br>
  When running a sparc with a serial console, certain types of interrupts would
  cause great grief.<br>
! <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/2.7/sparc/034_zsconsole.patch">
  A source code patch exists which remedies this problem.</a>
  <p>
  <li id="execsubr">
  <font color="#009000"><strong>033: RELIABILITY FIX: Nov 6, 2000</strong></font>
  &nbsp; <i>All architectures</i><br>
  Invalid fields in the exec header could cause a crash.<br>
! <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/2.7/common/033_execsubr.patch">
  A source code patch exists which remedies this problem.</a>
  <p>
  <li id="xtrans">
--- 127,147 ----
  &nbsp; <i>All architectures</i><br>
  Hostile servers can force OpenSSH clients to do agent or X11 forwarding.
  This problem is fixed as of OpenSSH 2.3.0.<br>
! <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.7/common/035_sshforwarding.patch">
  A source code patch exists which remedies this problem.</a>
  <p>
  <li id="zsconsole">
  <font color="#009000"><strong>034: RELIABILITY FIX: Nov 10, 2000</strong></font><br>
  When running a sparc with a serial console, certain types of interrupts would
  cause great grief.<br>
! <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.7/sparc/034_zsconsole.patch">
  A source code patch exists which remedies this problem.</a>
  <p>
  <li id="execsubr">
  <font color="#009000"><strong>033: RELIABILITY FIX: Nov 6, 2000</strong></font>
  &nbsp; <i>All architectures</i><br>
  Invalid fields in the exec header could cause a crash.<br>
! <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.7/common/033_execsubr.patch">
  A source code patch exists which remedies this problem.</a>
  <p>
  <li id="xtrans">
***************
*** 153,159 ****
  <a href="http://www.securityfocus.com/archive/1/139436">BUGTRAQ</a>
  mailing list.
  <br>
! <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/2.7/common/032_xtrans.patch">
  A source code patch exists which remedies this problem.</a>
  <p>
  <li id="httpd">
--- 153,159 ----
  <a href="http://www.securityfocus.com/archive/1/139436">BUGTRAQ</a>
  mailing list.
  <br>
! <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.7/common/032_xtrans.patch">
  A source code patch exists which remedies this problem.</a>
  <p>
  <li id="httpd">
***************
*** 164,170 ****
  to be exposed under certain configurations when these modules are used.
  (These modules are not active by default).
  <br>
! <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/2.7/common/031_httpd.patch">
  A source code patch exists which remedies this problem.</a>
  <p>
  <li id="telnetd">
--- 164,170 ----
  to be exposed under certain configurations when these modules are used.
  (These modules are not active by default).
  <br>
! <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.7/common/031_httpd.patch">
  A source code patch exists which remedies this problem.</a>
  <p>
  <li id="telnetd">
***************
*** 173,179 ****
  The telnet daemon does not strip out the TERMINFO, TERMINFO_DIRS, TERMPATH
  and TERMCAP (when it starts with a '/') environment variables.
  <br>
! <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/2.7/common/030_telnetd.patch">
  A source code patch exists which remedies this problem.</a>
  <p>
  <li id="sendmail">
--- 173,179 ----
  The telnet daemon does not strip out the TERMINFO, TERMINFO_DIRS, TERMPATH
  and TERMCAP (when it starts with a '/') environment variables.
  <br>
! <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.7/common/030_telnetd.patch">
  A source code patch exists which remedies this problem.</a>
  <p>
  <li id="sendmail">
***************
*** 181,187 ****
  &nbsp; <i>All architectures</i><br>
  There is a non-exploitable buffer overflow in sendmail's test mode.
  <br>
! <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/2.7/common/029_sendmail.patch">
  A source code patch exists which remedies this problem.</a>
  <p>
  <li id="format_strings">
--- 181,187 ----
  &nbsp; <i>All architectures</i><br>
  There is a non-exploitable buffer overflow in sendmail's test mode.
  <br>
! <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.7/common/029_sendmail.patch">
  A source code patch exists which remedies this problem.</a>
  <p>
  <li id="format_strings">
***************
*** 189,195 ****
  &nbsp; <i>All architectures</i><br>
  There are printf-style format string bugs in several privileged programs.
  <br>
! <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/2.7/common/028_format_strings.patch">
  A source code patch exists which remedies this problem.</a>
  <p>
  <li id="curses">
--- 189,195 ----
  &nbsp; <i>All architectures</i><br>
  There are printf-style format string bugs in several privileged programs.
  <br>
! <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.7/common/028_format_strings.patch">
  A source code patch exists which remedies this problem.</a>
  <p>
  <li id="curses">
***************
*** 199,205 ****
  as well as in the TERMCAP environment variable for setuid and setgid
  applications.
  <br>
! <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/2.7/common/027_curses.patch">
  A source code patch exists which remedies this problem.</a>
  <p>
  <li id="talkd">
--- 199,205 ----
  as well as in the TERMCAP environment variable for setuid and setgid
  applications.
  <br>
! <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.7/common/027_curses.patch">
  A source code patch exists which remedies this problem.</a>
  <p>
  <li id="talkd">
***************
*** 208,214 ****
  A format string vulnerability exists in talkd(8).  It is not clear
  yet what the impact is.
  <br>
! <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/2.7/common/026_talkd.patch">
  A source code patch exists which remedies this problem.</a>
  <p>
  <li id="pw_error">
--- 208,214 ----
  A format string vulnerability exists in talkd(8).  It is not clear
  yet what the impact is.
  <br>
! <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.7/common/026_talkd.patch">
  A source code patch exists which remedies this problem.</a>
  <p>
  <li id="pw_error">
***************
*** 220,233 ****
  <pre>
  # chmod u-s /usr/bin/chpass
  </pre>
! <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/2.7/common/025_pw_error.patch">
  A source code patch exists which remedies this problem.</a>
  <p>
  <li id="ipsec">
  <font color="#009000"><strong>024: SECURITY FIX: Sep 18, 2000</strong></font>
  &nbsp; <i>All architectures</i><br>
  Bad ESP/AH packets could cause a crash under certain conditions.
! <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/2.7/common/024_ipsec.patch"><br>
  A source code patch exists which remedies this problem.</a>
  <p>
  <li id="xlock">
--- 220,233 ----
  <pre>
  # chmod u-s /usr/bin/chpass
  </pre>
! <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.7/common/025_pw_error.patch">
  A source code patch exists which remedies this problem.</a>
  <p>
  <li id="ipsec">
  <font color="#009000"><strong>024: SECURITY FIX: Sep 18, 2000</strong></font>
  &nbsp; <i>All architectures</i><br>
  Bad ESP/AH packets could cause a crash under certain conditions.
! <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.7/common/024_ipsec.patch"><br>
  A source code patch exists which remedies this problem.</a>
  <p>
  <li id="xlock">
***************
*** 238,244 ****
  <pre>
  # chmod u-s /usr/X11R6/bin/xlock
  </pre>
! <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/2.7/common/023_xlock.patch">
  A source code patch exists which remedies this problem.</a>
  <p>
  <li id="mac68k_arandom">
--- 238,244 ----
  <pre>
  # chmod u-s /usr/X11R6/bin/xlock
  </pre>
! <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.7/common/023_xlock.patch">
  A source code patch exists which remedies this problem.</a>
  <p>
  <li id="mac68k_arandom">
***************
*** 283,289 ****
      the XFree86 Xwrapper already has tests for bad arguments.
  </ul>
  <br>
! <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/2.7/common/021_X11_libs.patch">
  A source code patch exists which remedies this problem.</a>
  <strong>Note 1:</strong> tcl/tk is required to build X11 from source.<br>
  <strong>Note 2:</strong> When re-building use the command
--- 283,289 ----
      the XFree86 Xwrapper already has tests for bad arguments.
  </ul>
  <br>
! <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.7/common/021_X11_libs.patch">
  A source code patch exists which remedies this problem.</a>
  <strong>Note 1:</strong> tcl/tk is required to build X11 from source.<br>
  <strong>Note 2:</strong> When re-building use the command
***************
*** 303,309 ****
  <a href=stable.html>stable release source tree</a> or apply the
  provided patch to a 2.7 source tree.
  <br>
! <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/2.7/pmax/020_pmax_msgbuf.patch">
  A source code patch exists which remedies this problem.</a>
  <p>
  <li id="ftpd">
--- 303,309 ----
  <a href=stable.html>stable release source tree</a> or apply the
  provided patch to a 2.7 source tree.
  <br>
! <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.7/pmax/020_pmax_msgbuf.patch">
  A source code patch exists which remedies this problem.</a>
  <p>
  <li id="ftpd">
***************
*** 313,319 ****
  ftpd had a remote root hole in it.  Luckily, ftpd was not enabled by default.
  The problem exists if anonymous ftp is enabled.
  <br>
! <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/2.7/common/019_ftpd.patch">
  A source code patch exists which remedies this problem.</a>
  <p>
  <li id="mopd">
--- 313,319 ----
  ftpd had a remote root hole in it.  Luckily, ftpd was not enabled by default.
  The problem exists if anonymous ftp is enabled.
  <br>
! <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.7/common/019_ftpd.patch">
  A source code patch exists which remedies this problem.</a>
  <p>
  <li id="mopd">
***************
*** 321,327 ****
  &nbsp; <i>All architectures</i><br>
  Mopd contained a buffer overflow.
  <br>
! <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/2.7/common/018_mopd.patch">
  A source code patch exists which remedies this problem.</a>
  <p>
  <li id="screen">
--- 321,327 ----
  &nbsp; <i>All architectures</i><br>
  Mopd contained a buffer overflow.
  <br>
! <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.7/common/018_mopd.patch">
  A source code patch exists which remedies this problem.</a>
  <p>
  <li id="screen">
***************
*** 332,338 ****
  screen-3.9.5.tgz.old and a replacement package has been provided under the
  name screen-3.9.5p1.tgz.
  <br>
! <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/2.7/ports/017_screen.patch">
  A source code patch exists which remedies this problem.</a>
  <p>
  <li id="xlhash">
--- 332,338 ----
  screen-3.9.5.tgz.old and a replacement package has been provided under the
  name screen-3.9.5p1.tgz.
  <br>
! <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.7/ports/017_screen.patch">
  A source code patch exists which remedies this problem.</a>
  <p>
  <li id="xlhash">
***************
*** 342,348 ****
  filter from working correctly on the 3c905B, thus preventing many IPv6 things
  from working.
  <br>
! <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/2.7/i386/016_xlhash.patch">
  A source code patch exists which remedies this problem.</a>
  <p>
  <li id="ste">
--- 342,348 ----
  filter from working correctly on the 3c905B, thus preventing many IPv6 things
  from working.
  <br>
! <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.7/i386/016_xlhash.patch">
  A source code patch exists which remedies this problem.</a>
  <p>
  <li id="ste">
***************
*** 352,358 ****
  (i.e., the D-Link 550TX) has a bug which causes the machine to panic at
  boot-time.
  <br>
! <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/2.7/i386/015_ste.patch">
  A source code patch exists which remedies this problem.</a>
  <p>
  <li id="pcvt">
--- 352,358 ----
  (i.e., the D-Link 550TX) has a bug which causes the machine to panic at
  boot-time.
  <br>
! <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.7/i386/015_ste.patch">
  A source code patch exists which remedies this problem.</a>
  <p>
  <li id="pcvt">
***************
*** 362,368 ****
  fixes a problem with scrolling region handling that has been seen by many
  users trying to use the BitchX irc client with the screen program.<br>
  <br>
! <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/2.7/i386/014_pcvt.patch">
  A source code patch exists which remedies this problem.</a>
  This is the second revision of the patch.
  <p>
--- 362,368 ----
  fixes a problem with scrolling region handling that has been seen by many
  users trying to use the BitchX irc client with the screen program.<br>
  <br>
! <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.7/i386/014_pcvt.patch">
  A source code patch exists which remedies this problem.</a>
  This is the second revision of the patch.
  <p>
***************
*** 373,379 ****
  That behaviour is not nice; this does not turn into a security problem in
  any real world situation that we know of, but a patch is available anyways.
  <br>
! <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/2.7/common/013_libedit.patch">
  A source code patch exists which remedies this problem.</a>
  <p>
  <li id="dhclient">
--- 373,379 ----
  That behaviour is not nice; this does not turn into a security problem in
  any real world situation that we know of, but a patch is available anyways.
  <br>
! <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.7/common/013_libedit.patch">
  A source code patch exists which remedies this problem.</a>
  <p>
  <li id="dhclient">
***************
*** 382,388 ****
  A serious bug in dhclient(8) could allow strings from a malicious dhcp
  server to be executed in the shell as root.
  <br>
! <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/2.7/common/012_dhclient.patch">
  A source code patch exists which remedies this problem.</a>
  <p>
  <li id="if_an">
--- 382,388 ----
  A serious bug in dhclient(8) could allow strings from a malicious dhcp
  server to be executed in the shell as root.
  <br>
! <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.7/common/012_dhclient.patch">
  A source code patch exists which remedies this problem.</a>
  <p>
  <li id="if_an">
***************
*** 391,397 ****
  Aironet Communications 4500/4800 IEEE 802.11DS driver has a bug which prevents
  <a href="http://man.openbsd.org/?query=ancontrol&amp;sektion=8">ancontrol(8)</a> from working correctly, instead causing a panic.
  <br>
! <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/2.7/i386/011_an.patch">
  A source code patch exists which remedies this problem.</a>
  <p>
  <li id="amiga_cd">
--- 391,397 ----
  Aironet Communications 4500/4800 IEEE 802.11DS driver has a bug which prevents
  <a href="http://man.openbsd.org/?query=ancontrol&amp;sektion=8">ancontrol(8)</a> from working correctly, instead causing a panic.
  <br>
! <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.7/i386/011_an.patch">
  A source code patch exists which remedies this problem.</a>
  <p>
  <li id="amiga_cd">
***************
*** 423,429 ****
  A serious bug in isakmpd(8) policy handling wherein policy
  verification could be completely bypassed in isakmpd.
  <br>
! <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/2.7/common/009_isakmpd.patch">
  A source code patch exists which remedies this problem.</a>
  <p>
  <li id="msdosfs">
--- 423,429 ----
  A serious bug in isakmpd(8) policy handling wherein policy
  verification could be completely bypassed in isakmpd.
  <br>
! <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.7/common/009_isakmpd.patch">
  A source code patch exists which remedies this problem.</a>
  <p>
  <li id="msdosfs">
***************
*** 431,437 ****
  &nbsp; <i>All architectures</i><br>
  Some operations in msdosfs could result in a system panic.
  <br>
! <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/2.7/common/008_msdosfs.patch">
  A source code patch exists which remedies this problem.</a>
  <p>
  <li id="cd9660">
--- 431,437 ----
  &nbsp; <i>All architectures</i><br>
  Some operations in msdosfs could result in a system panic.
  <br>
! <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.7/common/008_msdosfs.patch">
  A source code patch exists which remedies this problem.</a>
  <p>
  <li id="cd9660">
***************
*** 439,445 ****
  &nbsp; <i>All architectures</i><br>
  NFS exporting of CD filesystems caused a system panic.
  <br>
! <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/2.7/common/007_cd9660.patch">
  A source code patch exists which remedies this problem.</a>
  <p>
  <li id="uselogin">
--- 439,445 ----
  &nbsp; <i>All architectures</i><br>
  NFS exporting of CD filesystems caused a system panic.
  <br>
! <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.7/common/007_cd9660.patch">
  A source code patch exists which remedies this problem.</a>
  <p>
  <li id="uselogin">
***************
*** 455,461 ****
  Parse IPv4 options more carefully.  It is not yet clear if this can even be used
  to crash the machine remote or locally.
  <br>
! <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/2.7/common/005_ipopts.patch">
  A source code patch exists which remedies this problem.</a>
  <p>
  <li id="route">
--- 455,461 ----
  Parse IPv4 options more carefully.  It is not yet clear if this can even be used
  to crash the machine remote or locally.
  <br>
! <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.7/common/005_ipopts.patch">
  A source code patch exists which remedies this problem.</a>
  <p>
  <li id="route">
***************
*** 463,469 ****
  &nbsp; <i>All architectures</i><br>
  Certain routing table modifications by the superuser could cause a system panic.
  <br>
! <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/2.7/common/004_route.patch">
  A source code patch exists which remedies this problem.</a>
  <p>
  <li id="bridge">
--- 463,469 ----
  &nbsp; <i>All architectures</i><br>
  Certain routing table modifications by the superuser could cause a system panic.
  <br>
! <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.7/common/004_route.patch">
  A source code patch exists which remedies this problem.</a>
  <p>
  <li id="bridge">
***************
*** 473,479 ****
  go directly to the machine acting as a
  <a href="http://man.openbsd.org/?query=bridge&amp;sektion=4">bridge</a>.
  <br>
! <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/2.7/common/003_bridge.patch">
  A source code patch exists which remedies this problem.</a>
  <p>
  <li id="ef">
--- 473,479 ----
  go directly to the machine acting as a
  <a href="http://man.openbsd.org/?query=bridge&amp;sektion=4">bridge</a>.
  <br>
! <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.7/common/003_bridge.patch">
  A source code patch exists which remedies this problem.</a>
  <p>
  <li id="ef">
***************
*** 483,489 ****
  <a href="http://man.openbsd.org/?query=ef&amp;sektion=4">ef(4)</a>
  driver will complain when adding an address with ifconfig
  (ifconfig: SIOCAIFADDR: Invalid argument).<br>
! <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/2.7/common/002_ef.patch">
  A source code patch exists which remedies this problem.</a>
  <p>
  <li id="ipf">
--- 483,489 ----
  <a href="http://man.openbsd.org/?query=ef&amp;sektion=4">ef(4)</a>
  driver will complain when adding an address with ifconfig
  (ifconfig: SIOCAIFADDR: Invalid argument).<br>
! <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.7/common/002_ef.patch">
  A source code patch exists which remedies this problem.</a>
  <p>
  <li id="ipf">
***************
*** 491,497 ****
  &nbsp; <i>All architectures</i><br>
  A misuse of ipf(8)
  <i>keep-state</i> rules can result in firewall rules being bypassed.<br>
! <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/2.7/common/001_ipf.patch">
  A source code patch exists which remedies this problem.</a>
  It updates ipf to version 3.3.16.
  <p>
--- 491,497 ----
  &nbsp; <i>All architectures</i><br>
  A misuse of ipf(8)
  <i>keep-state</i> rules can result in firewall rules being bypassed.<br>
! <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.7/common/001_ipf.patch">
  A source code patch exists which remedies this problem.</a>
  It updates ipf to version 3.3.16.
  <p>