[1mSYNOPSIS[0m
[1mkinit [22m[[1m-V[22m] [[1m-l [4m[22mlifetime[24m] [[1m-s [4m[22mstart_time[24m] [[1m-r [4m[22mrenewable_life[24m] [[1m-p [22m| [1m-P[22m]
[[1m-f [22m| [1m-F[22m] [[1m-a[22m] [[1m-A[22m] [[1m-C[22m] [[1m-E[22m] [[1m-v[22m] [[1m-R[22m] [[1m-k [22m[[1m-t [4m[22mkeytab_file[24m]]
[[1m-c [4m[22mcache_name[24m] [[1m-n[22m] [[1m-S [4m[22mservice_name[24m][[1m-T [4m[22marmor_ccache[24m] [[1m-X[0m
[4mattribute[24m[=[4mvalue[24m]] [[4mprincipal[24m]
[1mDESCRIPTION[0m
[4mkinit[24m obtains and caches an initial ticket-granting ticket for [4mprinci-[0m
[4mpal[24m.
[1mOPTIONS[0m
[1m-V [22mdisplay verbose output.
[1m-l [4m[22mlifetime[0m
requests a ticket with the lifetime [4mlifetime[24m. The value for
[4mlifetime[24m must be followed immediately by one of the following
delimiters:
[1ms [22mseconds
[1mm [22mminutes
[1mh [22mhours
[1md [22mdays
as in "kinit -l 90m". You cannot mix units; a value of `3h30m'
will result in an error.
If the [1m-l [22moption is not specified, the default ticket lifetime
(configured by each site) is used. Specifying a ticket lifetime
longer than the maximum ticket lifetime (configured by each
site) results in a ticket with the maximum lifetime.
[1m-s [4m[22mstart_time[0m
requests a postdated ticket, valid starting at [4mstart_time[24m.
Postdated tickets are issued with the [4minvalid[24m flag set, and need
to be fed back to the kdc before use.
[1m-r [4m[22mrenewable_life[0m
requests renewable tickets, with a total lifetime of [4mrenew-[0m
[4mable_life[24m. The duration is in the same format as the [1m-l [22moption,
with the same delimiters.
[1m-f [22mrequest forwardable tickets.
[1m-F [22mdo not request forwardable tickets.
[1m-p [22mrequest proxiable tickets.
[1m-P [22mdo not request proxiable tickets.
[1m-a [22mrequest tickets with the local address[es].
[1m-A [22mrequest address-less tickets.
[1m-k [22m[[1m-t [4m[22mkeytab_file[24m]
requests a ticket, obtained from a key in the local host's
[4mkeytab[24m file. The name and location of the keytab file may be
specified with the [1m-t [4m[22mkeytab_file[24m option; otherwise the default
name and location will be used. By default a host ticket is
requested but any principal may be specified. On a KDC, the spe-
cial keytab location [1mKDB: [22mcan be used to indicate that kinit
should open the KDC database and look up the key directly. This
permits an administrator to obtain tickets as any principal that
supports password-based authentication.
[1m-n [22mRequests anonymous processing. Two types of anonymous princi-
pals are supported. For fully anonymous Kerberos, configure
pkinit on the KDC and configure [4mpkinit_anchors[24m in the client's
krb5.conf. Then use the [1m-n [22moption with a principal of the form
[4m@REALM[24m (an empty principal name followed by the at-sign and a
realm name). If permitted by the KDC, an anonymous ticket will
be returned. A second form of anonymous tickets is supported;
these realm-exposed tickets hide the identity of the client but
not the client's realm. For this mode, use [1mkinit -n [22mwith a nor-
mal principal name. If supported by the KDC, the principal (but
not realm) will be replaced by the anonymous principal. As of
release 1.8, the MIT Kerberos KDC only supports fully anonymous
operation.
[1m-T [4m[22marmor_ccache[0m
Specifies the name of a credential cache that already contains a
ticket. If supported by the KDC, This ccache will be used to
armor the request so that an attacker would have to know both
the key of the armor ticket and the key of the principal used
for authentication in order to attack the request. Armoring also
makes sure that the response from the KDC is not modified in
transit.
[1m-c [4m[22mcache_name[0m
use [4mcache_name[24m as the Kerberos 5 credentials (ticket) cache name
and location; if this option is not used, the default cache name
and location are used.
The default credentials cache may vary between systems. If the
[1mKRB5CCNAME [22menvironment variable is set, its value is used to
name the default ticket cache. If a principal name is specified
and the type of the default credentials cache supports a collec-
tion (such as the DIR type), an existing cache containing cre-
dentials for the principal is selected or a new one is created
and becomes the new primary cache. Otherwise, any existing con-
tents of the default cache are destroyed by [4mkinit[24m.
[1m-S [4m[22mservice_name[0m
specify an alternate service name to use when getting initial
tickets.
[1mflag_RSA_PROTOCOL[22m[=yes]
specify use of RSA, rather than the default Diffie-Hellman protocol
[1mENVIRONMENT[0m
[1mKinit [22muses the following environment variables:
KRB5CCNAME Location of the default Kerberos 5 credentials (ticket)
cache, in the form [4mtype[24m:[4mresidual[24m. If no type prefix is
present, the [1mFILE [22mtype is assumed. The type of the
default cache may determine the availability of a cache
collection; for instance, a default cache of type [1mDIR[0m
causes caches within the directory to be present in the
collection.
[1mFILES[0m
/tmp/krb5cc_[uid] default location of Kerberos 5 credentials cache
([uid] is the decimal UID of the user).
/etc/krb5.keytab default location for the local host's [1mkeytab [22mfile.
[1mSEE ALSO[0m
klist(1), kdestroy(1), kswitch(1), kerberos(1)
KINIT(1)
Man(1) output converted with
man2html