Thank you very much for the response.
>manually since its just an md4 hash with no salt, something like:
># echo -n password | iconv -t UTF-16LE | openssl dgst -md4
>And compare with the key in the keytab:
># klist -Kekt krb5.keytab
I have derived the key manually by using the below command:
# e
If I understand the concern, I have the same one. For user cron jobs, the
traditional approach is for the user to create a keytab. As others have noted,
the keytab is equivalent to the password. The problem for me is that a keytab
is good on all hosts. So if someone manages to become root on one
On Tue, Jun 6, 2017 at 11:48 AM, Ashi1986 wrote:
>>manually since its just an md4 hash with no salt, something like:
>># echo -n password | iconv -t UTF-16LE | openssl dgst -md4
>>And compare with the key in the keytab:
>># klist -Kekt krb5.keytab
>
> I have derived the key manually by using the b
On Tue, Jun 06, 2017 at 01:48:58AM -0700, Ashi1986 wrote:
> Thank you very much for the response.
>
> >manually since its just an md4 hash with no salt, something like:
> ># echo -n password | iconv -t UTF-16LE | openssl dgst -md4
> >And compare with the key in the keytab:
> ># klist -Kekt krb5.ke
Thanks for your response.
>>If so, you might try to apply manually the diff from the commit that
>>Robbie mentioned already.
I am new to open source, can you please share the link from where I can get
the commit sources.
Thank You
--
View this message in context:
http://kerberos.996246.n3.na
