typo fixes that have accrued in OpenBSD's import of OpenSSL over
the years
Index: MacOS/GetHTTPS.src/ErrorHandling.hpp
===================================================================
RCS file: /cvs/src/lib/libssl/src/MacOS/GetHTTPS.src/ErrorHandling.hpp,v
retrieving revision 1.1.1.1
retrieving revision 1.2
diff -u -p -r1.1.1.1 -r1.2
--- MacOS/GetHTTPS.src/ErrorHandling.hpp 5 Sep 2002 12:51:29 -0000
1.1.1.1
+++ MacOS/GetHTTPS.src/ErrorHandling.hpp 26 May 2007 00:36:03 -0000
1.2
@@ -29,7 +29,7 @@ OSErr AppendErrorMessageToHandle(Handle
-// A bunch of evil macros that would be uneccessary if I were always using
C++ !
+// A bunch of evil macros that would be unnecessary if I were always using
C++ !
#define SetErrorMessageAndBailIfNil(theArg,theMessage)
\
{
\
Index: crypto/asn1/a_bytes.c
===================================================================
RCS file: /cvs/src/lib/libssl/src/crypto/asn1/a_bytes.c,v
retrieving revision 1.1.1.4
retrieving revision 1.8
diff -u -p -r1.1.1.4 -r1.8
--- crypto/asn1/a_bytes.c 6 Sep 2008 12:15:39 -0000 1.1.1.4
+++ crypto/asn1/a_bytes.c 6 Sep 2008 12:17:48 -0000 1.8
@@ -79,7 +79,7 @@ ASN1_STRING *d2i_ASN1_type_bytes(ASN1_ST
if (tag >= 32)
{
- i=ASN1_R_TAG_VALUE_TOO_HIGH;;
+ i=ASN1_R_TAG_VALUE_TOO_HIGH;
goto err;
}
if (!(ASN1_tag2bit(tag) & type))
Index: crypto/asn1/t_x509.c
===================================================================
RCS file: /cvs/src/lib/libssl/src/crypto/asn1/t_x509.c,v
retrieving revision 1.1.1.5
retrieving revision 1.11
diff -u -p -r1.1.1.5 -r1.11
--- crypto/asn1/t_x509.c 9 Jan 2009 12:13:51 -0000 1.1.1.5
+++ crypto/asn1/t_x509.c 9 Jan 2009 12:15:27 -0000 1.11
@@ -332,7 +332,7 @@ int X509_signature_print(BIO *bp, X509_A
int ASN1_STRING_print(BIO *bp, ASN1_STRING *v)
{
int i,n;
- char buf[80],*p;;
+ char buf[80],*p;
if (v == NULL) return(0);
n=0;
Index: crypto/bn/bntest.c
===================================================================
RCS file: /cvs/src/lib/libssl/src/crypto/bn/bntest.c,v
retrieving revision 1.1.1.7
retrieving revision 1.12
diff -u -p -r1.1.1.7 -r1.12
--- crypto/bn/bntest.c 6 Sep 2008 12:15:41 -0000 1.1.1.7
+++ crypto/bn/bntest.c 6 Sep 2008 12:17:49 -0000 1.12
@@ -926,7 +926,7 @@ int test_mod_exp(BIO *bp, BN_CTX *ctx)
BN_bntest_rand(b,2+i,0,0); /**/
if (!BN_mod_exp(d,a,b,c,ctx))
- return(00);
+ return(0);
if (bp != NULL)
{
@@ -1028,7 +1028,7 @@ int test_exp(BIO *bp, BN_CTX *ctx)
BN_bntest_rand(b,2+i,0,0); /**/
if (!BN_exp(d,a,b,ctx))
- return(00);
+ return(0);
if (bp != NULL)
{
Index: crypto/des/times/usparc.cc
===================================================================
RCS file: /cvs/src/lib/libssl/src/crypto/des/times/usparc.cc,v
retrieving revision 1.1.1.1
retrieving revision 1.2
diff -u -p -r1.1.1.1 -r1.2
--- crypto/des/times/usparc.cc 5 Oct 1998 20:12:45 -0000 1.1.1.1
+++ crypto/des/times/usparc.cc 29 Mar 2005 17:29:10 -0000 1.2
@@ -2,7 +2,7 @@ solaris 2.5.1 usparc 167mhz?? - SC4.0 cc
For the ultra sparc, SunC 4.0 cc -fast -Xa -xO5, running 'des_opts'
gives a speed of 475,000 des/s while 'speed' gives 417,000 des/s.
-I belive the difference is tied up in optimisation that the compiler
+I believe the difference is tied up in optimisation that the compiler
is able to perform when the code is 'inlined'. For 'speed', the DES
routines are being linked from a library. I'll record the higher
speed since if performance is everything, you can always inline
Index: crypto/ripemd/README
===================================================================
RCS file: /cvs/src/lib/libssl/src/crypto/ripemd/README,v
retrieving revision 1.1.1.1
retrieving revision 1.2
diff -u -p -r1.1.1.1 -r1.2
--- crypto/ripemd/README 5 Oct 1998 20:12:41 -0000 1.1.1.1
+++ crypto/ripemd/README 29 Mar 2005 17:29:10 -0000 1.2
@@ -4,7 +4,7 @@ http://www.esat.kuleuven.ac.be/~bosselae
This is my implementation of RIPEMD-160. The pentium assember is a little
off the pace since I only get 1050 cycles, while the best is 1013.
I have a few ideas for how to get another 20 or so cycles, but at
-this point I will not bother right now. I belive the trick will be
+this point I will not bother right now. I believe the trick will be
to remove my 'copy X array onto stack' until inside the RIP1() finctions the
first time round. To do this I need another register and will only have one
temporary one. A bit tricky.... I can also cleanup the saving of the 5 words
Index: crypto/x509v3/v3_utl.c
===================================================================
RCS file: /cvs/src/lib/libssl/src/crypto/x509v3/v3_utl.c,v
retrieving revision 1.1.1.4
retrieving revision 1.9
diff -u -p -r1.1.1.4 -r1.9
--- crypto/x509v3/v3_utl.c 9 Jan 2009 12:14:01 -0000 1.1.1.4
+++ crypto/x509v3/v3_utl.c 9 Jan 2009 12:15:52 -0000 1.9
@@ -84,7 +84,7 @@ int X509V3_add_value(const char *name, c
CONF_VALUE *vtmp = NULL;
char *tname = NULL, *tvalue = NULL;
if(name && !(tname = BUF_strdup(name))) goto err;
- if(value && !(tvalue = BUF_strdup(value))) goto err;;
+ if(value && !(tvalue = BUF_strdup(value))) goto err;
if(!(vtmp = (CONF_VALUE *)OPENSSL_malloc(sizeof(CONF_VALUE)))) goto err;
if(!*extlist && !(*extlist = sk_CONF_VALUE_new_null())) goto err;
vtmp->section = NULL;
Index: doc/ssleay.txt
===================================================================
RCS file: /cvs/src/lib/libssl/src/doc/ssleay.txt,v
retrieving revision 1.1.1.3
retrieving revision 1.8
diff -u -p -r1.1.1.3 -r1.8
--- doc/ssleay.txt 6 Sep 2008 12:15:48 -0000 1.1.1.3
+++ doc/ssleay.txt 6 Sep 2008 12:17:52 -0000 1.8
@@ -3800,9 +3800,9 @@ made public on sci.crypt in Sep 1994 (RC
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.
Index: doc/ssl/SSL_CIPHER_get_name.pod
===================================================================
RCS file: /cvs/src/lib/libssl/src/doc/ssl/SSL_CIPHER_get_name.pod,v
retrieving revision 1.1.1.2
retrieving revision 1.4
diff -u -p -r1.1.1.2 -r1.4
--- doc/ssl/SSL_CIPHER_get_name.pod 29 Apr 2005 05:37:24 -0000 1.1.1.2
+++ doc/ssl/SSL_CIPHER_get_name.pod 29 Apr 2005 05:39:29 -0000 1.4
@@ -28,7 +28,7 @@ SSL_CIPHER_get_version() returns the pro
SSL_CIPHER_description() returns a textual description of the cipher used
into the buffer B<buf> of length B<len> provided. B<len> must be at least
-128 bytes, otherwise a pointer to the the string "Buffer too small" is
+128 bytes, otherwise a pointer to the string "Buffer too small" is
returned. If B<buf> is NULL, a buffer of 128 bytes is allocated using
OPENSSL_malloc(). If the allocation fails, a pointer to the string
"OPENSSL_malloc Error" is returned.
Index: doc/ssl/SSL_CTX_set_verify.pod
===================================================================
RCS file: /cvs/src/lib/libssl/src/doc/ssl/SSL_CTX_set_verify.pod,v
retrieving revision 1.1.1.3
retrieving revision 1.5
diff -u -p -r1.1.1.3 -r1.5
--- doc/ssl/SSL_CTX_set_verify.pod 11 Nov 2003 21:19:59 -0000 1.1.1.3
+++ doc/ssl/SSL_CTX_set_verify.pod 11 Nov 2003 22:15:19 -0000 1.5
@@ -28,7 +28,7 @@ specifies the B<verify_callback> functio
shall be specified, the NULL pointer can be used for B<verify_callback>. In
this case last B<verify_callback> set specifically for this B<ssl> remains. If
no special B<callback> was set before, the default callback for the underlying
-B<ctx> is used, that was valid at the the time B<ssl> was created with
+B<ctx> is used, that was valid at the time B<ssl> was created with
L<SSL_new(3)|SSL_new(3)>.
SSL_CTX_set_verify_depth() sets the maximum B<depth> for the certificate chain
Index: doc/ssl/SSL_SESSION_free.pod
===================================================================
RCS file: /cvs/src/lib/libssl/src/doc/ssl/SSL_SESSION_free.pod,v
retrieving revision 1.1.1.1
retrieving revision 1.3
diff -u -p -r1.1.1.1 -r1.3
--- doc/ssl/SSL_SESSION_free.pod 5 Sep 2002 12:51:22 -0000 1.1.1.1
+++ doc/ssl/SSL_SESSION_free.pod 21 Jun 2003 01:38:55 -0000 1.3
@@ -14,7 +14,7 @@ SSL_SESSION_free - free an allocated SSL
SSL_SESSION_free() decrements the reference count of B<session> and removes
the B<SSL_SESSION> structure pointed to by B<session> and frees up the
allocated
-memory, if the the reference count has reached 0.
+memory, if the reference count has reached 0.
=head1 NOTES
Index: doc/ssl/SSL_free.pod
===================================================================
RCS file: /cvs/src/lib/libssl/src/doc/ssl/SSL_free.pod,v
retrieving revision 1.1.1.1
retrieving revision 1.3
diff -u -p -r1.1.1.1 -r1.3
--- doc/ssl/SSL_free.pod 5 Sep 2002 12:51:22 -0000 1.1.1.1
+++ doc/ssl/SSL_free.pod 21 Jun 2003 01:38:55 -0000 1.3
@@ -14,7 +14,7 @@ SSL_free - free an allocated SSL structu
SSL_free() decrements the reference count of B<ssl>, and removes the SSL
structure pointed to by B<ssl> and frees up the allocated memory if the
-the reference count has reached 0.
+reference count has reached 0.
=head1 NOTES
Index: ssl/kssl.c
===================================================================
RCS file: /cvs/src/lib/libssl/src/ssl/kssl.c,v
retrieving revision 1.1.1.7
retrieving revision 1.8
diff -u -p -r1.1.1.7 -r1.8
--- ssl/kssl.c 6 Sep 2008 12:15:51 -0000 1.1.1.7
+++ ssl/kssl.c 6 Sep 2008 12:17:53 -0000 1.8
@@ -946,7 +946,7 @@ kssl_err_set(KSSL_ERR *kssl_err, int rea
if (kssl_err == NULL) return;
kssl_err->reason = reason;
- BIO_snprintf(kssl_err->text, KSSL_ERR_MAX, text);
+ BIO_snprintf(kssl_err->text, KSSL_ERR_MAX, "%s", text);
return;
}
Index: ssl/s3_clnt.c
===================================================================
RCS file: /cvs/src/lib/libssl/src/ssl/s3_clnt.c,v
retrieving revision 1.1.1.11
retrieving revision 1.21
diff -u -p -r1.1.1.11 -r1.21
--- ssl/s3_clnt.c 9 Jan 2009 12:14:07 -0000 1.1.1.11
+++ ssl/s3_clnt.c 9 Jan 2009 12:15:52 -0000 1.21
@@ -173,7 +173,7 @@ int ssl3_connect(SSL *s)
long num1;
void (*cb)(const SSL *ssl,int type,int val)=NULL;
int ret= -1;
- int new_state,state,skip=0;;
+ int new_state,state,skip=0;
RAND_add(&Time,sizeof(Time),0);
ERR_clear_error();
Index: test/times
===================================================================
RCS file: /cvs/src/lib/libssl/src/test/times,v
retrieving revision 1.1.1.1
retrieving revision 1.2
diff -u -p -r1.1.1.1 -r1.2
--- test/times 5 Oct 1998 20:13:05 -0000 1.1.1.1
+++ test/times 1 Aug 2005 19:44:53 -0000 1.2
@@ -68,7 +68,7 @@ eric (adding numbers to speculation)
--- Appendix ---
- The time measured is user time but these number a very rough.
- Remember this is the cost of both client and server sides of the protocol.
-- The TCP/kernal overhead of connection establishment is normally the
+- The TCP/kernel overhead of connection establishment is normally the
killer in SSL. Often delays in the TCP protocol will make session-id
reuse look slower that new sessions, but this would not be the case on
a loaded server.
______________________________________________________________________
OpenSSL Project http://www.openssl.org
Development Mailing List [email protected]
Automated List Manager [email protected]
