From a4b4e982f37cf6d3449d19ed58e2e6ca8b0aa02e Mon Sep 17 00:00:00 2001 From: Joseph Sutton Date: Wed, 21 Jun 2023 16:21:55 +1200 Subject: [PATCH] krb5: Fix code spelling Signed-off-by: Joseph Sutton --- lib/krb5/crypto.c | 8 ++++---- lib/krb5/init_creds_pw.c | 34 +++++++++++++++++----------------- lib/krb5/pac.c | 4 ++-- lib/krb5/store.c | 34 +++++++++++++++++----------------- 4 files changed, 40 insertions(+), 40 deletions(-) diff --git a/lib/krb5/crypto.c b/lib/krb5/crypto.c index d1258683f..b52f08466 100644 --- a/lib/krb5/crypto.c +++ b/lib/krb5/crypto.c @@ -3120,8 +3120,8 @@ krb5_crypto_prfplus(krb5_context context, * @param context Kerberos 5 context * @param crypto1 first key to combine * @param crypto2 second key to combine - * @param pepper1 factor to combine with first key to garante uniqueness - * @param pepper2 factor to combine with second key to garante uniqueness + * @param pepper1 factor to combine with first key to guarantee uniqueness + * @param pepper2 factor to combine with second key to guarantee uniqueness * @param enctype the encryption type of the resulting key * @param res allocated key, free with krb5_free_keyblock_contents() * @@ -3184,7 +3184,7 @@ _krb5_crypto_set_flags(krb5_context context, #ifndef HEIMDAL_SMALLER /** - * Deprecated: keytypes doesn't exists, they are really enctypes. + * Deprecated: keytypes don't exist, they are really enctypes. * * @ingroup krb5_deprecated */ @@ -3228,7 +3228,7 @@ krb5_keytype_to_enctypes (krb5_context context, } /** - * Deprecated: keytypes doesn't exists, they are really enctypes. + * Deprecated: keytypes don't exist, they are really enctypes. * * @ingroup krb5_deprecated */ diff --git a/lib/krb5/init_creds_pw.c b/lib/krb5/init_creds_pw.c index 1a649dfa9..e9e8228ae 100644 --- a/lib/krb5/init_creds_pw.c +++ b/lib/krb5/init_creds_pw.c @@ -1602,9 +1602,9 @@ enc_chal_step(krb5_context context, krb5_init_creds_context ctx, void *pa_ctx, P ppaid = process_pa_info(context, ctx->cred.client, a, &paid, in_md); /* - * If we don't have ppaid, ts because the KDC have not sent any - * salt info, lets to the first roundtrip so the KDC have a chance - * to send any. + * If we don't have ppaid, it's because the KDC has not sent any + * salt info. Let's do the first roundtrip so the KDC has a chance + * to send some. */ if (ppaid == NULL) { _krb5_debug(context, 5, "no ppaid found"); @@ -1760,7 +1760,7 @@ enc_ts_step(krb5_context context, krb5_init_creds_context ctx, void *pa_ctx, PA_ if (rep) { /* * Some KDC's don't send salt info in the reply when there is - * success pre-auth happned before, so use cached copy (or + * success pre-auth happened before, so use cached copy (or * even better, if there is just one pre-auth, save reply-key). */ if (ppaid == NULL && ctx->paid.etype != KRB5_ENCTYPE_NULL) { @@ -1779,15 +1779,15 @@ enc_ts_step(krb5_context context, krb5_init_creds_context ctx, void *pa_ctx, PA_ } /* - * If we don't have ppaid, ts because the KDC have not sent any - * salt info, lets to the first roundtrip so the KDC have a chance - * to send any. + * If we don't have ppaid, it's because the KDC has not sent any + * salt info. Let's do the first roundtrip so the KDC has a chance + * to send some. * * Don't bother guessing, it sounds like a good idea until you run * into KDCs that are doing failed auth counting based on the * ENC_TS tries. * - * Stashing the salt for the next run is a diffrent issue and + * Stashing the salt for the next run is a different issue and * could be considered in the future. */ @@ -1805,10 +1805,10 @@ enc_ts_step(krb5_context context, krb5_init_creds_context ctx, void *pa_ctx, PA_ /* * We have to allow the KDC to re-negotiate the PA-TS data - * once, this is since the in the case of a windows read only + * once, this is since a windows read only * KDC that doesn't have the keys simply guesses what the - * master is supposed to support. In the case where this - * breaks in when the RO-KDC is a newer version the the RW-KDC + * master is supposed to support. The case where this + * breaks is when the RO-KDC is a newer version than the RW-KDC * and the RO-KDC announced a enctype that the older doesn't * support. */ @@ -1958,7 +1958,7 @@ static const struct patype { */ pa_restart_f restart; /** - * Return 0 if the when complete, HEIM_ERR_PA_CONTINUE_NEEDED if more steps are require + * Return 0 when complete, HEIM_ERR_PA_CONTINUE_NEEDED if more steps are required */ pa_step_f step; pa_release_f release; @@ -2522,7 +2522,7 @@ krb5_init_creds_init(krb5_context context, /* FIXME should generate a new nonce for each AS-REQ */ krb5_generate_random_block (&ctx->nonce, sizeof(ctx->nonce)); ctx->nonce &= 0x7fffffff; - /* XXX these just needs to be the same when using Windows PK-INIT */ + /* XXX these just need to be the same when using Windows PK-INIT */ ctx->pk_nonce = ctx->nonce; ctx->prompter = prompter; @@ -2748,8 +2748,8 @@ krb5_init_creds_set_keytab(krb5_context context, ctx->keyproc = keytab_key_proc; /* - * We need to the KDC what enctypes we support for this keytab, - * esp if the keytab is really a password based entry, then the + * We need to tell the KDC what enctypes we support for this keytab, + * especially if the keytab is really a password based entry, then the * KDC might have more enctypes in the database then what we have * in the keytab. */ @@ -2766,7 +2766,7 @@ krb5_init_creds_set_keytab(krb5_context context, found = 1; - /* check if we ahve this kvno already */ + /* check if we have this kvno already */ if (entry.vno > kvno) { /* remove old list of etype */ if (etypes) @@ -3239,7 +3239,7 @@ init_creds_step(krb5_context context, ref_realm); /* - * If its a krbtgt, lets updat the requested krbtgt too + * If its a krbtgt, lets update the requested krbtgt too */ if (krb5_principal_is_krbtgt(context, ctx->cred.server)) { diff --git a/lib/krb5/pac.c b/lib/krb5/pac.c index e5b133f23..84015448c 100644 --- a/lib/krb5/pac.c +++ b/lib/krb5/pac.c @@ -151,7 +151,7 @@ static const struct heim_type_data pac_object = { /* * Returns the size of the PACTYPE header + the PAC_INFO_BUFFER array. This is * also the end of the whole thing, and any offsets to buffers from - * thePAC_INFO_BUFFER[] entries have to be beyond it. + * the PAC_INFO_BUFFER[] entries have to be beyond it. */ static krb5_error_code pac_header_size(krb5_context context, uint32_t num_buffers, uint32_t *result) @@ -724,7 +724,7 @@ verify_checksum(krb5_context context, * http://comments.gmane.org/gmane.comp.encryption.kerberos.devel/8743 * for the same issue in MIT, and * http://blogs.msdn.com/b/openspecification/archive/2010/01/01/verifying-the-server-signature-in-kerberos-privilege-account-certificate.aspx - * for Microsoft's explaination */ + * for Microsoft's explanation */ if (cksum.cksumtype == CKSUMTYPE_HMAC_MD5) { Checksum local_checksum; diff --git a/lib/krb5/store.c b/lib/krb5/store.c index e98dd4b96..01961f0e6 100644 --- a/lib/krb5/store.c +++ b/lib/krb5/store.c @@ -178,7 +178,7 @@ krb5_storage_seek(krb5_storage *sp, off_t offset, int whence) * Truncate the storage buffer in sp to offset. * * @param sp the storage buffer to truncate. - * @param offset the offset to truncate too. + * @param offset the offset to truncate to. * * @return An Kerberos 5 error code. * @@ -440,7 +440,7 @@ krb5_store_int(krb5_storage *sp, * Store a int32 to storage, byte order is controlled by the settings * on the storage, see krb5_storage_set_byteorder(). * - * @param sp the storage to write too + * @param sp the storage to write to * @param value the value to store * * @return 0 for success, or a Kerberos 5 error code on failure. @@ -463,7 +463,7 @@ krb5_store_int32(krb5_storage *sp, * Store a int64 to storage, byte order is controlled by the settings * on the storage, see krb5_storage_set_byteorder(). * - * @param sp the storage to write too + * @param sp the storage to write to * @param value the value to store * * @return 0 for success, or a Kerberos 5 error code on failure. @@ -490,7 +490,7 @@ krb5_store_int64(krb5_storage *sp, * Store a uint32 to storage, byte order is controlled by the settings * on the storage, see krb5_storage_set_byteorder(). * - * @param sp the storage to write too + * @param sp the storage to write to * @param value the value to store * * @return 0 for success, or a Kerberos 5 error code on failure. @@ -509,7 +509,7 @@ krb5_store_uint32(krb5_storage *sp, * Store a uint64 to storage, byte order is controlled by the settings * on the storage, see krb5_storage_set_byteorder(). * - * @param sp the storage to write too + * @param sp the storage to write to * @param value the value to store * * @return 0 for success, or a Kerberos 5 error code on failure. @@ -570,7 +570,7 @@ krb5_ret_int(krb5_storage *sp, * Read a int64 from storage, byte order is controlled by the settings * on the storage, see krb5_storage_set_byteorder(). * - * @param sp the storage to write too + * @param sp the storage to write to * @param value the value read from the buffer * * @return 0 for success, or a Kerberos 5 error code on failure. @@ -600,7 +600,7 @@ krb5_ret_int64(krb5_storage *sp, * Read a uint64 from storage, byte order is controlled by the settings * on the storage, see krb5_storage_set_byteorder(). * - * @param sp the storage to write too + * @param sp the storage to write to * @param value the value read from the buffer * * @return 0 for success, or a Kerberos 5 error code on failure. @@ -626,7 +626,7 @@ krb5_ret_uint64(krb5_storage *sp, * Read a int32 from storage, byte order is controlled by the settings * on the storage, see krb5_storage_set_byteorder(). * - * @param sp the storage to write too + * @param sp the storage to write to * @param value the value read from the buffer * * @return 0 for success, or a Kerberos 5 error code on failure. @@ -655,7 +655,7 @@ krb5_ret_int32(krb5_storage *sp, * Read a uint32 from storage, byte order is controlled by the settings * on the storage, see krb5_storage_set_byteorder(). * - * @param sp the storage to write too + * @param sp the storage to write to * @param value the value read from the buffer * * @return 0 for success, or a Kerberos 5 error code on failure. @@ -680,7 +680,7 @@ krb5_ret_uint32(krb5_storage *sp, uint32_t *value) * Store a int16 to storage, byte order is controlled by the settings * on the storage, see krb5_storage_set_byteorder(). * - * @param sp the storage to write too + * @param sp the storage to write to * @param value the value to store * * @return 0 for success, or a Kerberos 5 error code on failure. @@ -703,7 +703,7 @@ krb5_store_int16(krb5_storage *sp, * Store a uint16 to storage, byte order is controlled by the settings * on the storage, see krb5_storage_set_byteorder(). * - * @param sp the storage to write too + * @param sp the storage to write to * @param value the value to store * * @return 0 for success, or a Kerberos 5 error code on failure. @@ -722,7 +722,7 @@ krb5_store_uint16(krb5_storage *sp, * Read a int16 from storage, byte order is controlled by the settings * on the storage, see krb5_storage_set_byteorder(). * - * @param sp the storage to write too + * @param sp the storage to write to * @param value the value read from the buffer * * @return 0 for success, or a Kerberos 5 error code on failure. @@ -751,7 +751,7 @@ krb5_ret_int16(krb5_storage *sp, * Read a int16 from storage, byte order is controlled by the settings * on the storage, see krb5_storage_set_byteorder(). * - * @param sp the storage to write too + * @param sp the storage to write to * @param value the value read from the buffer * * @return 0 for success, or a Kerberos 5 error code on failure. @@ -776,7 +776,7 @@ krb5_ret_uint16(krb5_storage *sp, /** * Store a int8 to storage. * - * @param sp the storage to write too + * @param sp the storage to write to * @param value the value to store * * @return 0 for success, or a Kerberos 5 error code on failure. @@ -799,7 +799,7 @@ krb5_store_int8(krb5_storage *sp, /** * Store a uint8 to storage. * - * @param sp the storage to write too + * @param sp the storage to write to * @param value the value to store * * @return 0 for success, or a Kerberos 5 error code on failure. @@ -817,7 +817,7 @@ krb5_store_uint8(krb5_storage *sp, /** * Read a int8 from storage * - * @param sp the storage to write too + * @param sp the storage to write to * @param value the value read from the buffer * * @return 0 for success, or a Kerberos 5 error code on failure. @@ -840,7 +840,7 @@ krb5_ret_int8(krb5_storage *sp, /** * Read a uint8 from storage * - * @param sp the storage to write too + * @param sp the storage to write to * @param value the value read from the buffer * * @return 0 for success, or a Kerberos 5 error code on failure.