summaryrefslogtreecommitdiffstats
path: root/FAQ
diff options
context:
space:
mode:
authorDr. Stephen Henson <steve@openssl.org>2006-03-28 16:48:42 +0200
committerDr. Stephen Henson <steve@openssl.org>2006-03-28 16:48:42 +0200
commitf7a3296d8c8746b9901e95674425f300a6dfd1d4 (patch)
tree0d9d01e76d82315a99665e4711d6dc3b9f79a54d /FAQ
parentNew utility pkeyparam. Enhance and bugfix algorithm specific parameter (diff)
downloadopenssl-f7a3296d8c8746b9901e95674425f300a6dfd1d4.tar.xz
openssl-f7a3296d8c8746b9901e95674425f300a6dfd1d4.zip
Typo.
Diffstat (limited to 'FAQ')
-rw-r--r--FAQ4
1 files changed, 2 insertions, 2 deletions
diff --git a/FAQ b/FAQ
index cff1f69399..9f6dc63d4f 100644
--- 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.
-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
-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