Doc for GetChecksumHash method. about gokrb5 HOT 3 CLOSED

Hi, You are in the guts of the library here. If you are just using one of the etypes implemented you shouldn't need to worry too much about these inner workings. However I will try to answer your bullet points:

• protocolKey: this is the key obtained directly from the keytab or the sessionkey. From this the actual encryption key is derived using a method specific to the etype that also takes in the usage number.
• What the data is depends on what you are trying to achieve. Not sure I have enough to answer this one.
• usage: these are the usage constants as defined in RFC 4210 you'll find them all at https://github.com/jcmturner/gokrb5/blob/master/iana/keyusage/constants.go

I'm afraid if you are going to operate at this level you'll need to get very familiar with the kerberos RFCs.

You can see how I have created an encrypted authenticator here:
https://github.com/jcmturner/gokrb5/blob/master/messages/APReq.go#L66 which uses the crypto.GetEncryptedData method.

from gokrb5.

@jcmturner thank you for the answer.
Actually I was just following README and stuck on checksum calculation - https://github.com/jcmturner/gokrb5/blob/master/README.md#generic-kerberos-client.
My general goal - authenticate against Kafka Brokers with SASL and GSSAPI described here https://kafka.apache.org/protocol#sasl_handshake. As you see, not really much information about authentication.

from gokrb5.

gokrb5 doesn't currently implement SASL but does have some implementation of GSSAPI, that was needed to support SPNEGO, which may be of use to you.

I think what's needed is to implement some of these RFCs
https://tools.ietf.org/html/rfc4752#section-3.1
https://tools.ietf.org/html/rfc4422

from gokrb5.