Issues with rsh and kerberos
Rick Stevens
rstevens at vitalstream.com
Thu Feb 3 19:06:27 UTC 2005
Waldher, Travis R wrote:
>>-----Original Message-----
>>From: Rick Stevens [mailto:rstevens at vitalstream.com]
>>Sent: Tuesday, February 01, 2005 10:41 AM
>>To: Getting started with Red Hat Linux
>>Subject: Re: Issues with rsh and kerberos
>>
>>Waldher, Travis R wrote:
>>
>>>Ok..
>>>
>>>[user at machine ~]$ rsh hostname -n uptime
>>>krb_sendauth failed: You have no tickets cached
>>> 9:35am up 63 days, 19:33, 4 users, load average: 0.76, 0.61,
>
> 0.56
>
>>>Machine = RHEL client
>>>Hostname = HPUX 11.11 client
>>>
>>>I don't get the Kerberos error running this command against another
>
> RHEL
>
>>>machine.
>>>
>>>I have searched google and found nothing. Anyone else have any
>
> ideas?
>
>>I'll bet "hostname" was set up with kerberos user authentication,
>
> rather
>
>>than simple DES or MD5. That'd cause the error. By default, RHEL
>
> uses
>
>>MD5 (and/or DES), so no error would be no surprise.
>
>
> I would bet that is the case. As the HP systems don't use MD5 anywhere.
>
> Is there a way you know of, without changing the HP systems, to get rid
> of that error? (I can see calls from users on this when we go to the
> new NIS master running RHEL vs. the old running HP/UX.)
Create and cache a Kerberos ticket on the HP/UX machine for the machine
you're "rsh"ing from. You can use "krb5" to do this GUI-style, or
use "kadmin" for command-line operations. I hope you understand how
Kerberos works (realms, principals, etc.) or this will be VERY confusing
to you.
----------------------------------------------------------------------
- Rick Stevens, Senior Systems Engineer rstevens at vitalstream.com -
- VitalStream, Inc. http://www.vitalstream.com -
- -
- Grabel's Law: 2 is not equal to 3--not even for large values of 2. -
----------------------------------------------------------------------
More information about the Redhat-install-list
mailing list