projects
/
openssl.git
/ commitdiff
commit
grep
author
committer
pickaxe
?
search:
re
summary
|
shortlog
|
log
|
commit
| commitdiff |
tree
raw
|
patch
|
inline
| side by side (parent:
3e4585c
)
Typo.
author
Dr. Stephen Henson
<steve@openssl.org>
Tue, 28 Mar 2006 14:48:42 +0000
(14:48 +0000)
committer
Dr. Stephen Henson
<steve@openssl.org>
Tue, 28 Mar 2006 14:48:42 +0000
(14:48 +0000)
FAQ
patch
|
blob
|
history
diff --git
a/FAQ
b/FAQ
index cff1f69399459cafc770fbb70c35087836bb377a..9f6dc63d4fcf6781834008bd958463a44182c333 100644
(file)
--- a/
FAQ
+++ b/
FAQ
@@
-402,10
+402,10
@@
You can't generally create such a certificate using OpenSSL but there is no
need to any more. Nowadays web browsers using unrestricted strong encryption
are generally available.
need to any more. Nowadays web browsers using unrestricted strong encryption
are generally available.
-When there were tight
export
restrictions on the export of strong encryption
+When there were tight restrictions on the export of strong encryption
software from the US only weak encryption algorithms could be freely exported
(initially 40 bit and then 56 bit). It was widely recognised that this was
software from the US only weak encryption algorithms could be freely exported
(initially 40 bit and then 56 bit). It was widely recognised that this was
-inadequate. A relaxation the rules allowed the use of strong encryption but
+inadequate. A relaxation
of
the rules allowed the use of strong encryption but
only to an authorised server.
Two slighly different techniques were developed to support this, one used by
only to an authorised server.
Two slighly different techniques were developed to support this, one used by