summaryrefslogtreecommitdiff
path: root/ssl
diff options
context:
space:
mode:
authorDimitris Apostolou <dimitris.apostolou@icloud.com>2022-01-03 01:00:27 +0200
committerTomas Mraz <tomas@openssl.org>2022-01-05 12:37:20 +0100
commite304aa87b35fac5ea97c405dd3c21549faa45e78 (patch)
tree3a9330f9259ddf98984e63db297583b5ef9dcd7b /ssl
parente66c41725f03dae2b295df048312fe6d28729e98 (diff)
downloadopenssl-new-e304aa87b35fac5ea97c405dd3c21549faa45e78.tar.gz
Fix typos
Reviewed-by: Tim Hudson <tjh@openssl.org> Reviewed-by: Tomas Mraz <tomas@openssl.org> (Merged from https://github.com/openssl/openssl/pull/17392)
Diffstat (limited to 'ssl')
-rw-r--r--ssl/statem/statem_srvr.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/ssl/statem/statem_srvr.c b/ssl/statem/statem_srvr.c
index cda9b32156..283d55e9f0 100644
--- a/ssl/statem/statem_srvr.c
+++ b/ssl/statem/statem_srvr.c
@@ -2899,7 +2899,7 @@ static int tls_process_cke_rsa(SSL *s, PACKET *pkt)
* We must not leak whether a decryption failure occurs because of
* Bleichenbacher's attack on PKCS #1 v1.5 RSA padding (see RFC 2246,
* section 7.4.7.1). We use the special padding type
- * RSA_PKCS1_WITH_TLS_PADDING to do that. It will automaticaly decrypt the
+ * RSA_PKCS1_WITH_TLS_PADDING to do that. It will automatically decrypt the
* RSA, check the padding and check that the client version is as expected
* in the premaster secret. If any of that fails then the function appears
* to return successfully but with a random result. The call below could