===================================================================
RCS file: /cvsrepo/anoncvs/cvs/www/errata25.html,v
retrieving revision 1.78
retrieving revision 1.79
diff -u -r1.78 -r1.79
--- www/errata25.html	2019/05/27 22:55:19	1.78
+++ www/errata25.html	2019/05/28 16:32:41	1.79
@@ -84,16 +84,18 @@
 <hr>
 
 <ul>
+
 <li id="cron">
-<strong>SECURITY FIX: Aug 30, 1999</strong>
+<strong>001: SECURITY FIX: Aug 30, 1999</strong>
 &nbsp; <i>All architectures</i><br>
 In cron(8), make sure argv[] is NULL terminated in the fake popen() and
 run sendmail as the user, not as root.
 <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.5/common/012_cron.patch">
 A source code patch exists which remedies this problem.</a>
 <p>
+
 <li id="miscfs">
-<strong>SECURITY FIX: Aug 12, 1999</strong>
+<strong>002: SECURITY FIX: Aug 12, 1999</strong>
 &nbsp; <i>All architectures</i><br>
 The procfs and fdescfs filesystems had an overrun in their handling
 of uio_offset in their readdir() routines. (These filesystems are not
@@ -101,39 +103,44 @@
 <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.5/common/011_miscfs.patch">
 A source code patch exists which remedies this problem.</a>
 <p>
+
 <li id="profil">
-<strong>SECURITY FIX: Aug 9, 1999</strong>
+<strong>003: SECURITY FIX: Aug 9, 1999</strong>
 &nbsp; <i>All architectures</i><br>
 Stop profiling (see profil(2)) when we execve() a new process.
 <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.5/common/010_profil.patch">
 A source code patch exists which remedies this problem.</a>
 <p>
+
 <li id="ipsec_in_use">
-<strong>SECURITY FIX: Aug 6, 1999</strong>
+<strong>004: SECURITY FIX: Aug 6, 1999</strong>
 &nbsp; <i>All architectures</i><br>
 Packets that should have been handled by IPsec may be transmitted
 as cleartext. PF_KEY SA expirations may leak kernel resources.
 <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.5/common/009_ipsec_in_use.patch">
 A source code patch exists which remedies this problem.</a>
 <p>
+
 <li id="rc">
-<strong>SECURITY FIX: Aug 5, 1999</strong>
+<strong>005: SECURITY FIX: Aug 5, 1999</strong>
 &nbsp; <i>All architectures</i><br>
 In /etc/rc, use mktemp(1) for motd re-writing, and change the find(1)
 to use -execdir.
 <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.5/common/008_rc.patch">
 A source code patch exists which remedies this problem.</a>
 <p>
+
 <li id="chflags">
-<strong>SECURITY FIX: Jul 30, 1999</strong>
+<strong>006: SECURITY FIX: Jul 30, 1999</strong>
 &nbsp; <i>All architectures</i><br>
 Do not permit regular users to chflags(2) or fchflags(2) on character or
 block devices which they may currently be the owner of.
 <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.5/common/007_chflags.patch">
 A source code patch exists which remedies this problem.</a>
 <p>
+
 <li id="nroff">
-<strong>SECURITY FIX: Jul 27, 1999</strong>
+<strong>007: SECURITY FIX: Jul 27, 1999</strong>
 &nbsp; <i>All architectures</i><br>
 Cause groff(1) to be invoked with the -S flag, when called by nroff(1),
 to avoid various groff features which may be security issues.  On the
@@ -142,40 +149,45 @@
 <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.5/common/006_nroff.patch">
 A source code patch exists which remedies this problem.</a>
 <p>
+
 <li id="fts">
-<strong>RELIABILITY FIX: May 19, 1999</strong>
+<strong>008: RELIABILITY FIX: May 19, 1999</strong>
 &nbsp; <i>All architectures</i><br>
 Programs using fts(3) could dump core when given a directory structure
 with a very large number of entries.
 <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.5/common/005_fts.patch">
 A source code patch exists which remedies this problem.</a>
 <p>
+
 <li id="tcpsack">
-<strong>RELIABILITY FIX: May 19, 1999</strong>
+<strong>009: RELIABILITY FIX: May 19, 1999</strong>
 &nbsp; <i>All architectures</i><br>
 Sequence numbers could wrap with TCP_SACK and TCP_NEWRENO, resulting in
 failure to retransmit correctly.
 <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.5/common/004_tcpsack.patch">
 A source code patch exists which remedies this problem.</a>
 <p>
+
 <li id="ipsec1">
-<strong>RELIABILITY FIX</strong>
+<strong>010: RELIABILITY FIX</strong>
 &nbsp; <i>All architectures</i><br>
 Retransmitted TCP packets could get corrupted when flowing over an
 IPSEC ESP tunnel.
 <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.5/common/003_espdata.patch">
 A source code patch exists which remedies this problem.</a>
 <p>
+
 <li id="bmap">
-<strong>RELIABILITY FIX</strong>
+<strong>011: RELIABILITY FIX</strong>
 &nbsp; <i>All architectures</i><br>
 A local user can crash the system by reading a file larger than 64meg
 from an ext2fs partition.
 <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.5/common/002_bmap.patch">
 A source code patch exists which remedies this problem.</a>
 <p>
+
 <li id="pfkey">
-<strong>RELIABILITY FIX</strong>
+<strong>012: RELIABILITY FIX</strong>
 &nbsp; <i>All architectures</i><br>
 PF_KEY socket operations leak internal kernel resources, so that a
 system running an IPsec key management daemon like photurisd or isakmpd
@@ -184,31 +196,35 @@
 <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.5/common/001_pfkey.patch">
 A source code patch exists which remedies this problem.</a>
 <p>
+
 <li id="y2k">
-<strong>Y2K FIX: Aug 30, 1999</strong><br>
+<strong>013: Y2K FIX: Aug 30, 1999</strong><br>
 This patch corrects various OpenBSD/i386 2.5 problems with Y2K. The 2.6
 release (released at 1 Dec 1999) has this problem solved. This patch is
 just a workaround.
 <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.5/i386/014_y2k.patch">
 A source code patch exists which remedies this problem.</a>
 <p>
+
 <li id="brooktree">
-<strong>RELIABILITY FIX</strong><br>
+<strong>014: RELIABILITY FIX</strong><br>
 If a user opened the brooktree device on a system where it did not exist,
 the kernel crashed.
 <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.5/i386/013_brooktree.patch">
 A source code patch exists which remedies this problem.</a>
 <p>
+
 <li id="macutils">
-<strong>INSTALL PROBLEM</strong><br>
+<strong>015: INSTALL PROBLEM</strong><br>
 The mac68k install utils were mistakenly left off the CD and out of
 the FTP install directories.  These tools have now been added to the
 FTP install directories.  See
 <a href="https://ftp.openbsd.org/pub/OpenBSD/2.5/mac68k/utils">
 https://ftp.openbsd.org/pub/OpenBSD/2.5/mac68k/utils</a>
 <p>
+
 <li id="powerpc_trap">
-<strong>RELIABILITY FIX</strong><br>
+<strong>016: RELIABILITY FIX</strong><br>
 Two problems in the powerpc kernel trap handling cause severe system
 unreliability.
 <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.5/powerpc/001_trap.patch">