*Fisher Yu*
- * Enable AES and SHA3 optimisations on Applie Silicon M3-based MacOS systems
+ * Enable AES and SHA3 optimisations on Apple Silicon M3-based MacOS systems
similar to M1/M2.
*Tom Cosgrove*
this switch breaks interoperability with correct implementations.
* Fix a use after free bug in d2i_X509_PUBKEY when overwriting a
- re-used X509_PUBKEY object if the second PUBKEY is malformed.
+ reused X509_PUBKEY object if the second PUBKEY is malformed.
*Bernd Edlinger*
*Billy Bob Brumley, Nicola Tuveri*
* Fix a use after free bug in d2i_X509_PUBKEY when overwriting a
- re-used X509_PUBKEY object if the second PUBKEY is malformed.
+ reused X509_PUBKEY object if the second PUBKEY is malformed.
*Bernd Edlinger*
*Bodo Moeller*
* Store verify_result within SSL_SESSION also for client side to
- avoid potential security hole. (Re-used sessions on the client side
+ avoid potential security hole. (Reused sessions on the client side
always resulted in verify_result==X509_V_OK, not using the original
result of the server certificate verification.)
* Optimized AES-CTR for ARM Neoverse V1 and V2
- * Enable AES and SHA3 optimisations on Applie Silicon M3-based MacOS systems
+ * Enable AES and SHA3 optimisations on Apple Silicon M3-based MacOS systems
similar to M1/M2.
* Various optimizations for cryptographic routines using RISC-V vector crypto
/*
* VMS C only for now, implemented in vms_decc_init.c
* If other C compilers forget to terminate argv with NULL, this function
- * can be re-used.
+ * can be reused.
*/
char **copy_argv(int *argc, char *argv[]);
# endif
#include "internal/numbers.h"
/*
- * When we do a lookup/insert/delete, there is a high likelyhood
+ * When we do a lookup/insert/delete, there is a high likelihood
* that we will iterate over at least part of the neighborhood list
* As such, because we design a neighborhood entry to fit into a single
* cache line it is advantageous, when supported to fetch the entire
=item V
-Vector Extention for Application Processors
+Vector Extension for Application Processors
Could be detected using hwprobe for Linux kernel >= 6.5
/*
* We need at least 11 bytes to be able to do anything here
- * 1 byte to detect the operation to preform, 2 bytes
+ * 1 byte to detect the operation to perform, 2 bytes
* for the lookup key, and 8 bytes of value
*/
if (len < 11) {
end:
CT_POLICY_EVAL_CTX_free(ctx);
/*
- * With SSL_VERIFY_NONE the session may be cached and re-used despite a
+ * With SSL_VERIFY_NONE the session may be cached and reused despite a
* failure return code here. Also the application may wish the complete
* the handshake, and then disconnect cleanly at a higher layer, after
* checking the verification status of the completed connection.
|| !TEST_ptr(kdf2 = EVP_KDF_fetch(NULL, LN_tls1_prf, NULL))
|| !test_kdfs_same(kdf1, kdf2))
ok = 0;
- /* kdf1 is re-used below, so don't free it here */
+ /* kdf1 is reused below, so don't free it here */
EVP_KDF_free(kdf2);
kdf2 = NULL;
"-in", $b_csr])));
ok(-e $ca_serial_dot_in_dir);
-# Tests for explict start and end dates of certificates
+# Tests for explicit start and end dates of certificates
my %today = (strftime("%Y-%m-%d", gmtime) => 1);
my $enddate;
ok(run(app(["openssl", "x509", "-req", "-text",
OSSL_DISPATCH_END
};
-/* We're re-using most XOR keymgmt functions also for signature operations: */
+/* We're reusing most XOR keymgmt functions also for signature operations: */
static void *xor_xorhmacsig_gen(void *genctx, OSSL_CALLBACK *osslcb, void *cbarg)
{
XORKEY *k = xor_gen(genctx, osslcb, cbarg);