Lines Matching full:realms

79 responses. The @samp{realms} section contains information about specific
80 realms, such as where they hide their KDC@. This section serves the same
83 mappings from domains to realms, equivalent to the Kerberos 4
84 @file{krb.realms} file.
92 [realms]
107 @samp{kerberos.my.realm}, you can omit the @samp{realms} section too.
179 me@@MY.REALMS's Password:
370 [realms]
567 useful when you have multiple realms to distribute from one server.
739 It is possible to share keys between two realms that trust each
817 destination realm adds its peer to the "transited-realms" field in the
819 if one of the transited-realms changed the order of the list. For the
821 the transited realms must be listed as trusted in the @code{[capaths]}
830                 SERVER-REALM = PERMITTED-CROSS-REALMS ...
839 @code{SU.SE} realms to authenticate to services in
860 Be careful of which realm goes where; it's easy to put realms in the
864 authenticating.  After the equal sign go all the realms that the
867 The order of the @code{PERMITTED-CROSS-REALMS} is not important when
882 For client configuration, the order of @code{PERMITTED-CROSS-REALMS}
892 @code{PERMITTED-CROSS-REALMS} section), and then from there to
896 the first realm in @code{PERMITTED-CROSS-REALMS} is used.  If, for
911 divide systems, services, and users into child realms (perhaps based
914 authentications to and from the child realms.
918 @code{WIN.EXAMPLE.COM}, and then child Active Directory realms
920 goal is to allow users in any of these realms to authenticate to
921 services in any of these realms.  The @code{EXAMPLE.COM} KDC (and
940 and @code{SALES.WIN.EXAMPLE.COM} realms to authenticate to services in
943 @code{WIN.EXAMPLE.COM} to reach these realms.  Both sides of the
948 @c    kmumble transit-check client server transit-realms ...
996 that clients can be redirected by an attacker to realms within the
1000 An example configuration that informs clients that for the realms
1445 [realms]
1618 [realms]