version 1.15, 1998/02/24 00:30:49 |
version 1.16, 1998/03/06 12:19:07 |
|
|
use be <a href=policy.html>freely available and with good licenses</a>. |
use be <a href=policy.html>freely available and with good licenses</a>. |
We do not use cryptography with nasty patents. |
We do not use cryptography with nasty patents. |
We also require that such software is from countries with useful export |
We also require that such software is from countries with useful export |
licenses because we do not wish to break the laws of any country.<p> |
licenses because we do not wish to break the laws of any country. |
|
The cryptographic software components which we use currently were |
|
written in Argentina, Australia, Canada, Germany, Greece, Norway, and |
|
Sweden. |
|
<p> |
|
|
When we create OpenBSD releases or snapshots we build our release |
When we create OpenBSD releases or snapshots we build our release |
binaries in free countries to assure that the sources and binaries we |
binaries in free countries to assure that the sources and binaries we |
provide to users are free of tainting. In the past our release binary |
provide to users are free of tainting. In the past our release binary |
builds have been done in Canada, Sweden, and Germany.<p> |
builds have been done in Canada, Sweden, and Germany.<p> |
|
|
|
OpenBSD ships with Kerberos IV included. The codebase we use is the |
|
exportable KTH-based release from Sweden. Kerberos V support will |
|
perhaps appear in 1999, but at present time a freely exportable |
|
Kerberos V release does not exist.<p> |
|
|
Today cryptography is an important means for enhancing the <a |
Today cryptography is an important means for enhancing the <a |
href=security.html>security</a> of an operating system. The |
href=security.html>security</a> of an operating system. The |