The innerContext is Kerberos, so I'd like to see the
Mechanism and innerContextToken, so I can then decode the
innerContextToken as Krb5 and see the ticket, etc.
I can see the TGS-REP coming back to the client before it started GSS
with the server. I have the server's keytab file. Shouldn't
Brian Atkins wrote:
> I'm trying to decode the GSS-API conversation between a client and
> server. I can see the traffic on the designated port, but when I select
> "Decode As", the GSS-API protocol doesn't appear.
It's not a "protocol" *per se*. It's not something that usually (if
ever) occu
