|| M_METHOD == M_METHOD_WSARECVMSG
# if defined(__APPLE__)
/*
- * CMSG_SPACE is not a constant expresson on OSX even though POSIX
+ * CMSG_SPACE is not a constant expression on OSX even though POSIX
* says it's supposed to be. This should be adequate.
*/
# define BIO_CMSG_ALLOC_LEN 64
OSSL_CMP_CTX *ctx; /* CMP client context reused for transactionID etc. */
void *custom_ctx; /* application-specific server context */
int certReqId; /* of ir/cr/kur, OSSL_CMP_CERTREQID_NONE for p10cr */
- int polling; /* current tranaction is in polling mode */
+ int polling; /* current transaction is in polling mode */
OSSL_CMP_SRV_cert_request_cb_t process_cert_request;
OSSL_CMP_SRV_rr_cb_t process_rr;
memcpy(q++, p, sizeof(*q));
/*
- * Note that OSSL_CIPHER_PARAM_AEAD_IVLEN is a synomym for
+ * Note that OSSL_CIPHER_PARAM_AEAD_IVLEN is a synonym for
* OSSL_CIPHER_PARAM_IVLEN so both are covered here.
*/
p = OSSL_PARAM_locate_const(params, OSSL_CIPHER_PARAM_IVLEN);
my $ZT8 = $_[20]; # [clobbered] ZMM temporary
my $PBLOCK_LEN = $_[21]; # [in] partial block length
my $GH = $_[22]; # [in] ZMM with hi product part
- my $GM = $_[23]; # [in] ZMM with mid prodcut part
+ my $GM = $_[23]; # [in] ZMM with mid product part
my $GL = $_[24]; # [in] ZMM with lo product part
my $label_suffix = $label_count++;
$code.=<<___;
ld1 {$ivec1.4s},[$ivp]
ld1 {@datax[0].4s,@datax[1].4s,@datax[2].4s,@datax[3].4s},[$inp],#64
- // note ivec1 and vtmpx[3] are resuing the same register
+ // note ivec1 and vtmpx[3] are reusing the same register
// care needs to be taken to avoid conflict
eor @vtmp[0].16b,@vtmp[0].16b,$ivec1.16b
ld1 {@vtmpx[0].4s,@vtmpx[1].4s,@vtmpx[2].4s,@vtmpx[3].4s},[$inp],#64
$code.=<<___;
ld1 {$ivec1.4s},[$ivp]
ld1 {@datax[0].4s,@datax[1].4s,@datax[2].4s,@datax[3].4s},[$inp],#64
- // note ivec1 and vtmpx[3] are resuing the same register
+ // note ivec1 and vtmpx[3] are reusing the same register
// care needs to be taken to avoid conflict
eor @vtmp[0].16b,@vtmp[0].16b,$ivec1.16b
ld1 {@vtmpx[0].4s,@vtmpx[1].4s,@vtmpx[2].4s,@vtmpx[3].4s},[$inp],#64
The method to be looked up should be identified with data found in I<data>
(which is the I<mcm_data> that was passed to ossl_construct_method()).
In other words, the ossl_method_construct() caller is entirely responsible
-for ensuring the necesssary data is made available.
+for ensuring the necessary data is made available.
Optionally, I<prov> may be given as a search criterion, to narrow down the
search of a method belonging to just one provider.
* The stateless reset token manager is responsible for mapping stateless reset
* tokens to connections. It is used to identify stateless reset tokens in
* incoming packets. In this regard it can be considered an alternate "routing"
- * mechanism for incoming packets, and is somewhat analagous with the LCIDM,
+ * mechanism for incoming packets, and is somewhat analogous with the LCIDM,
* except that it uses SRTs to route rather than DCIDs.
*
* The SRTM specifically stores a bidirectional mapping of the form
}
/*
- * Ony assign context gen_type if it was set by dsa_gen_type_name2id
+ * Only assign context gen_type if it was set by dsa_gen_type_name2id
* must be in range:
* DSA_PARAMGEN_TYPE_FIPS_186_4 <= gen_type <= DSA_PARAMGEN_TYPE_FIPS_DEFAULT
*/
/*
* The Full(0) certificate decodes to a seemingly valid X.509
* object with a plausible key, so the TLSA record is well
- * formed. However, we don't actually need the certifiate for
+ * formed. However, we don't actually need the certificate for
* usages PKIX-EE(1) or DANE-EE(3), because at least the EE
* certificate is always presented by the peer. We discard the
* certificate, and just use the TLSA data as an opaque blob
* mode. DHE PSK will not be used for sure, because in any case where
* it would be supported (i.e. if a key share is present), NO_DHE would
* be supported as well. As the latter is preferred it would be
- * choosen. By removing DHE PSK here, we don't have to deal with the
+ * chosen. By removing DHE PSK here, we don't have to deal with the
* SSL_OP_PREFER_NO_DHE_KEX option in any other place.
*/
s->ext.psk_kex_mode = TLSEXT_KEX_MODE_FLAG_KE;
$proxy->start() or plan skip_all => "Unable to start up Proxy for tests";
plan tests => 1;
my $alert = TLSProxy::Message->alert();
-ok(TLSProxy::Message->fail() && !$alert->server() && !$alert->encrypted(), "Client sends an unecrypted alert");
+ok(TLSProxy::Message->fail() && !$alert->server() && !$alert->encrypted(), "Client sends an unencrypted alert");
sub alert_filter
{
/*
* Test TLS1.3 connection establishment succeeds with various configurations of
* the options `SSL_OP_ALLOW_NO_DHE_KEX` and `SSL_OP_PREFER_NO_DHE_KEX`.
- * The verification of whether the right KEX mode is choosen is not covered by
+ * The verification of whether the right KEX mode is chosen is not covered by
* this test but by `test_tls13kexmodes`.
*
* Tests (idx & 1): Server has `SSL_OP_ALLOW_NO_DHE_KEX` set.
if (!TEST_int_eq(SSL_get_error(clientssl, 0), SSL_ERROR_WANT_WRITE))
goto end;
- /* Allow one write to progess, but the next one to signal retry */
+ /* Allow one write to progress, but the next one to signal retry */
if (!TEST_true(BIO_ctrl(bretry, MAYBE_RETRY_CTRL_SET_RETRY_AFTER_CNT, 1,
NULL)))
goto end;