spelling and add `Configuring AFS clients' subsection

git-svn-id: svn://svn.h5l.se/heimdal/trunk/heimdal@11920 ec53bebd-3082-4978-b11e-865c3cabbd6b
This commit is contained in:
Love Hörnquist Åstrand
2003-03-26 09:54:28 +00:00
parent 6bea5a83bc
commit d83bf67207

View File

@@ -94,9 +94,9 @@ encryption types.
Its only possible (in all cases) to do this for DES encryption types because
only then the token (the AFS equivalent of a ticket) will be be smaller
than the maximum size that can fit in the token cache in
openafs/transarc client. Its so tight fit that some extra wrapping on the ASN1/DER encoding is removed from the Kerberos ticket.
OpenAFS/Transarc client. Its so tight fit that some extra wrapping on the ASN1/DER encoding is removed from the Kerberos ticket.
2b uses a Kerberos 5 EncTicketPart instead of a Kerberos 4 dito for
2b uses a Kerberos 5 EncTicketPart instead of a Kerberos 4 ditto for
the part of the ticket that is encrypted with the service's key. The
client doesn't know what's inside the encrypted data so to the client it doesn't matter.
@@ -117,3 +117,8 @@ them to the string list option @code{[kdc]use_2b} in the kdc's
use_2b = afs@@SU.SE
use_2b = afs/it.su.se@@SU.SE
@end example
@subsection Configuring AFS clients
There is no need to configure AFS clients. The only software that
needs to be installed/upgrade is a Kerberos 5 enabled file{afslog}.