===================================================================
RCS file: /cvsrepo/anoncvs/cvs/www/security.html,v
retrieving revision 1.93
retrieving revision 1.94
diff -c -r1.93 -r1.94
*** www/security.html	1999/04/18 02:34:01	1.93
--- www/security.html	1999/04/20 08:23:32	1.94
***************
*** 55,65 ****
  in mind.  Code often gets audited multiple times, and by multiple
  people with different auditing skills.<p>
  
! Some members of our security auditing team work for
! <a href=http://www.secnet.com>Secure Networks</a>, the company that
! makes the industry's premier network security scanning software
! package Ballista.
! This company does a lot of security research, and this fits in well
  with the OpenBSD stance.  OpenBSD passes Ballista's tests with flying
  colours.<p>
  
--- 55,65 ----
  in mind.  Code often gets audited multiple times, and by multiple
  people with different auditing skills.<p>
  
! Some members of our security auditing team worked for Secure Networks,
! the company that made the industry's premier network security scanning
! software package Ballista (Secure Networks got purchased by Network
! Associates, Ballista got renamed to Cybercop Scanner, and well...)
! That company did a lot of security research, and thus fit in well
  with the OpenBSD stance.  OpenBSD passes Ballista's tests with flying
  colours.<p>
  
***************
*** 77,85 ****
  been fixed in a previous release).  In other cases we have been saved
  from full exploitability of complex step-by-step attacks because we
  had fixed one of the intermediate steps.  An example of where we
! managed such a success is the
! <a href=http://www.secnet.com/sni-advisories/sni-19.bsd.lpd.advisory.html>
! lpd advisory from Secure Networks.</a><p>
  
  Our proactive auditing process has really paid off.  Statements like
  ``This problem was fixed in OpenBSD about 6 months ago'' have become
--- 77,84 ----
  been fixed in a previous release).  In other cases we have been saved
  from full exploitability of complex step-by-step attacks because we
  had fixed one of the intermediate steps.  An example of where we
! managed such a success is the lpd advisory that Secure Networks put out.
! <p>
  
  Our proactive auditing process has really paid off.  Statements like
  ``This problem was fixed in OpenBSD about 6 months ago'' have become
***************
*** 286,295 ****
  
  <p>
  <h3><font color=#e00000><strong>Other Resources</strong></font></h3>
- Other security advisories that have (in the past) affected OpenBSD can
- be found at the <a href=http://www.secnet.com/nav1.html>Secure Networks archive</a>.
- Some OpenBSD audit team members worked with Secure Networks on discovering
- and solving the problems detailed in some of their security advisories.
  
  <p> If you find a new security problem, you can mail it to
  <a href=mailto:deraadt@openbsd.org>deraadt@openbsd.org</a>.
--- 285,290 ----
***************
*** 301,307 ****
  <a href=index.html><img height=24 width=24 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.93 1999/04/18 02:34:01 deraadt Exp $</small>
  
  </body>
  </html>
--- 296,302 ----
  <a href=index.html><img height=24 width=24 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.94 1999/04/20 08:23:32 deraadt Exp $</small>
  
  </body>
  </html>