diff options
| -rw-r--r-- | doc/man3/EVP_PKEY_decrypt.pod | 2 | ||||
| -rw-r--r-- | doc/man3/RSA_public_encrypt.pod | 2 |
2 files changed, 2 insertions, 2 deletions
diff --git a/doc/man3/EVP_PKEY_decrypt.pod b/doc/man3/EVP_PKEY_decrypt.pod index 1f5d06b5b8..903d933fb2 100644 --- a/doc/man3/EVP_PKEY_decrypt.pod +++ b/doc/man3/EVP_PKEY_decrypt.pod @@ -68,7 +68,7 @@ of side-channel secure code from applications using OpenSSL. If OpenSSL is configured to use a provider that doesn't implement implicit rejection, the code still needs to handle the returned values using side-channel free code. -Side-channel free handling of the error stack can be peformed using +Side-channel free handling of the error stack can be performed using either a pair of unconditional L<ERR_set_mark(3)> and L<ERR_pop_to_mark(3)> calls or by using the L<ERR_clear_error(3)> call. diff --git a/doc/man3/RSA_public_encrypt.pod b/doc/man3/RSA_public_encrypt.pod index 5e0139b711..47d198a24c 100644 --- a/doc/man3/RSA_public_encrypt.pod +++ b/doc/man3/RSA_public_encrypt.pod @@ -102,7 +102,7 @@ a side-channel secure error handling. Applications that want to be secure against side-channel attacks with providers that don't implement implicit rejection, still need to handle the returned values using side-channel free code. -Side-channel free handling of the error stack can be peformed using +Side-channel free handling of the error stack can be performed using either a pair of unconditional L<ERR_set_mark(3)> and L<ERR_pop_to_mark(3)> calls or by using the L<ERR_clear_error(3)> call. |