Lara Adianto wrote:
>>In fact, MIT Kerberos 1.3 and higher does support
>>RC4-HMAC.
>>MIT Kerberos supports the broadest possible set of
>>enctypes
>>available to ensure interoperability with other
>>implementations.
>>
>
> Thank you for the reply Jeffrey.
>
> So, can I conclude that the encrypt
> In fact, MIT Kerberos 1.3 and higher does support
> RC4-HMAC.
> MIT Kerberos supports the broadest possible set of
> enctypes
> available to ensure interoperability with other
> implementations.
>
Thank you for the reply Jeffrey.
So, can I conclude that the encryption types that is
compatible wi
Lara Adianto wrote:
> My question is: how does the windows kerberos client
> know which encryption type that it must use for the
> encryption of this preauth-data ? As far as I know,
> the default encryption type for windows kerberos is
> RC4-HMAC, but MIT Kerberos only supports DES-CBC-CRC
> and D
Hi,
I have a doubt about the AS-REQ mechanism between a
windows client and an MIT KDC.
When the windows client sends an AS-REQ to the KDC,
the AS-REQ contains a preauthentication data (the
timestamp) which is encrypted using the key generated
from the hash of the user's password.
My question is:
