A keytab (key table) is a file containing pairs of kerberos principals and encryption keys. You can use a keytab file to do kerberos authentication without having to enter a password (the key is derived from your password). Keytab's are generally used for 2 reasons:
For a more complete explanation, see the MIT krb5 documentation: http://web.mit.edu/kerberos/krb5-latest/doc/basic/keytab_def.html
type t = Krb_internal_public.Std.Keytab.tmodule Path : sig ... endval load : Path.t -> t Async.Deferred.Or_error.tval validate : t -> Principal.t -> unit Async.Deferred.Or_error.tEnsure the keytab can be loaded successfully and contains an entry for the given principal. This does not verify whether the keytab is up to date, since it only performs offline checks.
val validate_path :
Path.t ->
Principal.Name.t ->
unit Async.Deferred.Or_error.tLike validate but takes a path and principal name
val entries_by_kvno :
t ->
Krb_internal_public.Std.Keytab_entry.t list Core.Int.Map.t
Async.Deferred.Or_error.tval entries_for_principal :
t ->
Principal.t ->
Krb_internal_public.Std.Keytab_entry.t list Async.Deferred.Or_error.tval add_spn : t -> Principal.Name.t -> unit Async.Deferred.Or_error.tval remove_spn : t -> Principal.Name.t -> unit Async.Deferred.Or_error.tval add_entry :
t ->
password:string ->
enctype:Krb_internal_public.Std.Enctype.t ->
kvno:int ->
principal:Principal.t ->
unit Async.Deferred.Or_error.tval add_new_entry_for_all_principals :
?kvno:int ->
t ->
password:string ->
unit Async.Deferred.Or_error.tFor each principal and enctype in the keytab, add a fresh key generated from the provided password.
module Stable : sig ... end