Created attachment 716755 [details]
strace log when connecting from a Linux machine
If you have telnet-server installed and enabled through xinetd, if you try to telnet to the Fedora 18 machine from another Linux machine, it immediately closes the connection after printing the /etc/issue.net file:
Fedora release 18 (Spherical Cow)
Kernel 3.7.2-201.fc18.i686.PAE on an i686 (3)
Connection closed by foreign host.
If you look in /var/log/secure on the Fedora 18 machine, you see:
Mar 26 17:04:36 C-STU11-Fedora login: FATAL: can't reopen tty: No such file or directory
If you telnet from a Windows machine, it works.
I changed in /etc/xinetd.d/telnet the server part to:
server = /bin/strace
server_args = -o /var/tmp/telnet.trace /usr/sbin/in.telnetd
and collected strace logs from connecting from Linux and Windows. I'll attach these.
Created attachment 716756 [details]
strace log when connecting from a Windows machine
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
Is this still an issue? I think it should be fixed now.
Nothing has happened with this package since I reported this bug, no updates have been issued (for Fedora 18), so yes this is still broken.
We fixed it in our own systems by removing this package and installing krb5-appl-servers instead.
I tried it on Fedora 19 and it works fine both as a systemd service or xinetd service, and nothing has changed in the code. The compiler flags have changed. Maybe the package in Fedora 18 was just broken by the compiler somehow.
I should have mentioned that this bug is actually caused by /usr/bin/login from util-linux package. Issue should be fixed in util-linux - 2.23.1-2. util-linux update should land in f18-updates-testing soon.
util-linux-2.22.2-7.fc18 has been submitted as an update for Fedora 18.
* should fix your issue,
* was pushed to the Fedora 18 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing util-linux-2.22.2-7.fc18'
as soon as you are able to.
Please go to the following url:
then log in and leave karma (feedback).
util-linux-2.22.2-7.fc18 has been pushed to the Fedora 18 stable repository. If problems still persist, please make note of it in this bug report.
Why was this update pushed? Does anyone read the QA reports on the admin.fedoraproject.org site? This is still very broken.
This message is a reminder that Fedora 18 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 18. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora
'version' of '18'.
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version prior to Fedora 18's end of life.
Thank you for reporting this issue and we are sorry that we may not be
able to fix it before Fedora 18 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged change the 'version' to a later Fedora
version prior to Fedora 18's end of life.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
Thank you for reporting this bug and we are sorry it could not be fixed.