summaryrefslogtreecommitdiffstats
path: root/doc/ssleay.txt
diff options
context:
space:
mode:
authorDr. Stephen Henson <steve@openssl.org>2009-02-14 21:49:38 +0000
committerDr. Stephen Henson <steve@openssl.org>2009-02-14 21:49:38 +0000
commit477fd4596feb89fe943130c8b1a4e37a0d3764bb (patch)
tree06e988b58c9127180ea9ce61841064bcfa736f9f /doc/ssleay.txt
parent30b1b28aff8911c6a39890e78f8358079a415353 (diff)
PR: 1835
Submitted by: Damien Miller <djm@mindrot.org> Approved by: steve@openssl.org Fix various typos.
Diffstat (limited to 'doc/ssleay.txt')
-rw-r--r--doc/ssleay.txt4
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/ssleay.txt b/doc/ssleay.txt
index c75312911f..a8b04d7059 100644
--- a/doc/ssleay.txt
+++ b/doc/ssleay.txt
@@ -3800,9 +3800,9 @@ made public on sci.crypt in Sep 1994 (RC4) and Feb 1996 (RC2). I have
copies of the origional postings if people are interested. RSA I believe
claim that they were 'trade-secrets' and that some-one broke an NDA in
revealing them. Other claim they reverse engineered the algorithms from
-compiled binaries. If the algorithms were reverse engineered, I belive
+compiled binaries. If the algorithms were reverse engineered, I believe
RSA had no legal leg to stand on. If an NDA was broken, I don't know.
-Regardless, RSA, I belive, is willing to go to court over the issue so
+Regardless, RSA, I believe, is willing to go to court over the issue so
licencing is probably the best idea, or at least talk to them.
If there are people who actually know more about this, pease let me know, I
don't want to vilify or spread miss-information if I can help it.