}
/*
- * Determine wheter a claim applies to the most specific objectClass of the
+ * Determine whether a claim applies to the most specific objectClass of the
* principal.
*/
static int claim_applies_to_class(TALLOC_CTX *mem_ctx,
uint32_t supported_session_etypes;
uint32_t available_enctypes = 0;
/*
- * also lagacy enctypes are announced,
+ * also legacy enctypes are announced,
* but effectively restricted by kdc_enctypes
*/
uint32_t domain_enctypes = ENC_RC4_HMAC_MD5 | ENC_RSA_MD5 | ENC_CRC32;
* authenticate the KDC to the LDAP server is highly likely to
* be circular.
*
- * In future we may set this up to use EXERNAL and SSL
+ * In future we may set this up to use EXTERNAL and SSL
* certificates, for now it will almost certainly be NTLMSSP_SET_USERNAME
*/
* from the password history, so we don't
* update the badPwdCount, but still return
* PREAUTH_FAILED and need to forward to
- * a RWDC in order to produce an autoritative
+ * a RWDC in order to produce an authoritative
* response for the client.
*/
status = NT_STATUS_WRONG_PASSWORD;
char *krb5_err_str = smb_get_krb5_error_message(context,
code,
mem_ctx);
- printf("%s: %s\n", msg, krb5_err_str ? krb5_err_str : "UNKOWN");
+ printf("%s: %s\n", msg, krb5_err_str ? krb5_err_str : "UNKNOWN");
talloc_free(mem_ctx);
exit(exit_code);
* ADDOM.SAMBA.EXAMPLE.COM
*
* We look up if we have and entry in the database and get an
- * entry with the pricipal:
+ * entry with the principal:
*
* cifs/dc7.SAMBA2008R2.EXAMPLE.COM@SAMBA2008R2.EXAMPLE.COM
*
* RODC, then we need to regenerate the PAC - we can't trust
* it, and confirm that the RODC was permitted to print this ticket
*
- * Becasue of the samba_kdc_validate_pac_blob() step we can be
+ * Because of the samba_kdc_validate_pac_blob() step we can be
* sure that the record in 'client' matches the SID in the
* original PAC.
*/