version 1.27, 1998/02/23 22:17:17 |
version 1.28, 1998/02/24 00:30:49 |
|
|
uncompromising view towards increased security than Sun, SGI, IBM, HP, |
uncompromising view towards increased security than Sun, SGI, IBM, HP, |
or other vendors are able to. We can make changes the vendors would |
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> |
not make. Also, since OpenBSD is exported with <a href=crypto.html> |
cryptography software</a>, we are able to take cryptographic |
cryptography software, we are able to take cryptographic |
approaches towards fixing security problems.<p> |
approaches towards fixing security problems.</a><p> |
|
|
Like most readers of the |
Like most readers of the |
<a href=http://www.geek-girl.com/bugtraq/index.html> |
<a href=http://www.geek-girl.com/bugtraq/index.html> |
|
|
the problems were in fact exploitable. This proactive auditing |
the problems were in fact exploitable. This proactive auditing |
process has really paid off. Statements like ``This problem was fixed |
process has really paid off. Statements like ``This problem was fixed |
in OpenBSD about 6 months ago'' have become commonplace in security |
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 |
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> |
<p> |
<h3><font color=#e00000><strong>OpenBSD 2.1 Security Advisories</strong></font></h3> |
<h3><font color=#e00000><strong>OpenBSD 2.1 Security Advisories</strong></font></h3> |