Bug 144248 (IT_60479)
Summary: | telnet does not pass on Umlauts | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 3 | Reporter: | Steffen Mann <smann> |
Component: | krb5 | Assignee: | Nalin Dahyabhai <nalin> |
Status: | CLOSED NOTABUG | QA Contact: | Brian Brock <bbrock> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 3.0 | CC: | sven.borkert, tao |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2005-09-29 17:41:00 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | |||
Bug Blocks: | 132991 |
Description
Steffen Mann
2005-01-05 11:44:22 UTC
*** Bug 144249 has been marked as a duplicate of this bug. *** From the duped bug: The weird looking characters should be german umlauts like the special characters for ae oe ue and sz. It seems to me that this is a problem with the telnet client only? When using a windows telnet client I don't get the problem, it only appears when makeing a telnet between two Red Hat machines. could you please provide the output of: $ which telnet Can your X-Terminal (xterm, konsole, gnome-terminal) display the Umlauts correctly? Does "ssh" work? Harald; [root@smann redhat]# which telnet /usr/kerberos/bin/telnet [root@smann redhat]# ssh does work, even windows telnet clients do. Gnome-terminal do display the Umlauts correct. which telnet /usr/kerberos/bin/telnet Interesting. /usr/bin/telnet does not have the Problem. Everything else works correctly. reassigning to kerberos Telnet is stripping off the high bit of characters you're inputting before sending them because the telnet binary option hasn't been negotiated. I'm not actually sure yet that this is a bug, because the telnet specs default to treating options which haven't been negotiated as if they were disabled. Either way, passing "-8" to telnet on the command line should force the telnet binary option to be negotiated, which will give you the results you're expecting. Closing because the telnet client is obeying the protocol specs, and there's a command-line option which provides the desired behavior. |