telnet using kerberos
03-22-2012 07:42 AM
We have reproduced the same issue on Red Hat Enterprise Linux Server 5.6 by using the latest release of Centrify Express for Linux and the Centrify-Enabled Kerberos Tools. We have escalated the issue to engineering for further investigation and will get back to you soon of our findings.
04-05-2012 05:16 PM
We made a typo above, we meant it is a bug in Centrify DirectControl for Express and we will address this issue in a future release, probably next.
01-21-2014 09:41 PM
A fresh install of latest stable version of Express Edition, on a stock, fully up-to-date centOS 5.10 system, and still seeing this error.
Just updating this thread.
We still need to resolve this small bug.
01-22-2014 05:22 AM
I have no visibility to when this will be resolved, but may I ask, why is TELNET being used?
If Keberos is being leveraged for the Authentication this means that there's a need to have some sort of security for the credential exchange; I can also safely assume that the data that you are taking countermeasures to encrypt the traffic in a different layer (maybe SSL or TLS).
If you're going through those lenghts, why not consider our commercial versions? Not only you'll get more capabilities, but you'll be in a better position to ask for this to be prioritized.