===================================================================
RCS file: /cvsrepo/anoncvs/cvs/www/security.html,v
retrieving revision 1.27
retrieving revision 1.28
diff -u -r1.27 -r1.28
--- www/security.html	1998/02/23 22:17:17	1.27
+++ www/security.html	1998/02/24 00:30:49	1.28
@@ -23,8 +23,8 @@
 uncompromising view towards increased security than Sun, SGI, IBM, HP,
 or other vendors are able to.  We can make changes the vendors would
 not make.  Also, since OpenBSD is exported with <a href=crypto.html>
-cryptography software</a>, we are able to take cryptographic
-approaches towards fixing security problems.<p>
+cryptography software, we are able to take cryptographic
+approaches towards fixing security problems.</a><p>
 
 Like most readers of the
 <a href=http://www.geek-girl.com/bugtraq/index.html>
@@ -55,11 +55,10 @@
 the problems were in fact exploitable.  This proactive auditing
 process has really paid off.  Statements like ``This problem was fixed
 in OpenBSD about 6 months ago'' have become commonplace in security
-forums like <a href=http://www.geek-girl.com/bugtraq/index.html>BUGTRAQ</a>.
+forums like <a href=http://www.geek-girl.com/bugtraq/index.html>BUGTRAQ</a>.<p>
 
-<p>
 The auditing process is not over yet, and as you can see we continue
-to find and fix new security flaws.
+to find and fix new security flaws.<p>
 
 <p>
 <h3><font color=#e00000><strong>OpenBSD 2.1 Security Advisories</strong></font></h3>
@@ -137,7 +136,7 @@
 <a href=index.html><img src=/back.gif border=0 alt=OpenBSD></a>
 <a href=mailto:www@openbsd.org>www@openbsd.org</a>
 <br>
-<small>$OpenBSD: security.html,v 1.27 1998/02/23 22:17:17 deraadt Exp $</small>
+<small>$OpenBSD: security.html,v 1.28 1998/02/24 00:30:49 deraadt Exp $</small>
 
 </body>
 </html>