Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
The kerberos aware telnet is not working on RHEL-6 with basic configuration. This can be considered as a regression, since it was working on RHEL-5.
Further investigation showed that this is due to des-cbc-crc encryption, which seems to be the only one that krb5-telnet supports. It looks like this encryption is suppressed by default in krb5-1.10, which is probably good, but maybe telnet should be changed too to support a stronger encoding.
I agree that telnet is quite a marginal service, but still, one might expect this is working.
Version-Release number of selected component (if applicable):
krb5-1.10.3
How reproducible:
always
Steps to Reproduce:
1. Set up KDC and start krb5-telnetd
2. Set up the client and get a TGT
# kinit test
Password for test:
kinit: Password incorrect while getting initial credentials
3. Try to connect with krb5-telnet.
# /usr/kerberos/bin/telnet -d
telnet>
telnet> toggle authdebug
auth debugging enabled
telnet> toggle debug
Won't turn on socket level debugging.
telnet>
telnet> open rhel6 -a -l test
Trying 192.168.100.60...
Connected to rhel6.pkis.net (192.168.100.60).
Escape character is '^]'.
>>>TELNET: I support auth type 2 6
>>>TELNET: I support auth type 2 2
>>>TELNET: I support auth type 2 0
>>>TELNET: auth_send got: 02 06 02 02 02 00
>>>TELNET: He supports 2
>>>TELNET: He supports 2
>>>TELNET: Trying 2 2
telnet: calling krb5_sname_to_principal
telnet: done calling krb5_sname_to_principal
telnet: Kerberos V5: failure on principal (No credentials cache found)
>>>TELNET: He supports 2
>>>TELNET: Trying 2 0
telnet: calling krb5_sname_to_principal
telnet: done calling krb5_sname_to_principal
telnet: Kerberos V5: failure on principal (No credentials cache found)
>>>TELNET: Sent failure message
Password:
telnet> q
Connection closed.
Actual results:
telnet does not works by default
Expected results:
telnet supports a stronger encryption
Additional info:
Comment 2RHEL Program Management
2013-10-13 23:43:16 UTC
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated
in the current release, Red Hat is unable to address this
request at this time.
Red Hat invites you to ask your support representative to
propose this request, if appropriate, in the next release of
Red Hat Enterprise Linux.