Red Hat Bugzilla – Bug 196376
Kerberized telnetd should default to /etc/issue.net as banner
Last modified: 2012-06-20 09:33:42 EDT
Description of problem:
/usr/sbin/in.telnetd uses /etc/issue.net as its default banner, making it easy
to change, should a custom banner be needed/desired.
/usr/kerberos/sbin/telnetd on the other hand uses a default of the hostname +
version info + the terminal name.
Getting them to display the same thing by default would be good, and
/etc/issue.net would be preferred over the kerberized default.
Version-Release number of selected component (if applicable): N/A
How reproducible: Always
Steps to Reproduce:
1. Set /etc/issue.net to something recognizable
2. Use /usr/kerberos/sbin/telnetd as the server for telnet service
3. Connect to system with telnet
4. Change telnet service to use /usr/sbin/in.telnetd as the server
5. Connect to system with telnet
Actual results: Different login banners are displayed
Expected results: The same login banner is displayed
Multiple resolutions are possible.
Currently there is code within telnetd.c which checks the default entry in
something (unsure if this is termcap or gettytab) for the 'im' characteristic,
and uses that if present for the banner. The BSDs have extended this to also
look for the 'if' characteristic, which is a file to use for the banner, and
which defaults to /etc/issue.
Alternatively, the %i handling code could be taken from the netkit version of
utility.c (in the putf function), and the default IM prepended with %%i.
Thank you for submitting this issue for consideration in Red Hat Enterprise Linux. The release for which you requested us to review is now End of Life.
Please See https://access.redhat.com/support/policy/updates/errata/
If you would like Red Hat to re-consider your feature request for an active release, please re-open the request via appropriate support channels and provide additional supporting details about the importance of this issue.