Upgrade to the Latest Version of MIT Kerberos on RHEL3.1

Aaron Grewell agrewell
Thu Aug 11 11:00:12 PDT 2005


On Wednesday 10 August 2005 21:25, A. Khattri wrote:
> On Wed, 10 Aug 2005, Net Llama! wrote:
> > On 08/10/2005 05:41 PM, James McDonald wrote:
> > > I have a Redhat Enterprise Linux Box at work which I have winbind
> > > authentication running successfully to handle remote logins via a
> > > kerberised version of telnet which is at version:
>
> Wow, I thought everyone knew how insecure telnet is...

Thus the 'kerberised' bit.  Correctly configured, Kerberos encrypts both 
authentication and payload of a telnet session, in addition to providing 
single sign on.  This can also be done with SSH, but it's much more complex.  
Given an existing Kerberos environment Telnet is quite a bit simpler while 
retaining a comparable level of security.

I went through a similar upgrade to the Kerberos modules on RHEL3 to make it 
compatible with MS Kerb, and used the same direct-overwrite method from 
source.  Kerberos libs are linked to so many things that even when you've got 
RPMS they won't upgrade due to version requirements of other packages.  
Trying to upgrade Kerb via RPM was a one-way ticket to Dependency Hell on the 
one system I tried it on.  The upgrade to RHEL 4 is easier, and includes a 
nice recent Kerb implementation.  I've been down the other road, and I 
recommend a full distro upgrade here if it's an option for you.  Really.


More information about the Linux-users mailing list