Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1520906 - make hostname in login(1) prompt optional [rhel-7.5]
make hostname in login(1) prompt optional [rhel-7.5]
Status: CLOSED ERRATA
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: util-linux (Show other bugs)
7.4
Unspecified Unspecified
unspecified Severity high
: rc
: ---
Assigned To: Karel Zak
Radka Skvarilova
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2017-12-05 07:50 EST by Karel Zak
Modified: 2018-04-10 13:28 EDT (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2018-04-10 13:27:15 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2018:0936 None None None 2018-04-10 13:28 EDT

  None (edit)
Description Karel Zak 2017-12-05 07:50:35 EST
Description of problem:

See https://bugzilla.redhat.com/show_bug.cgi?id=1448225#c22

Now login provides -H command line option to suppress hostname in the login prompt. Unfortunately, it's useless in some case (for example telnetd does not provide a way how to modify login(1) command line). 

For RHEL6.10 (and RHEL.9.Z) and upstream tree have been implemented a new /etc/login.defs option LOGIN_PLAIN_PROMPT to suppress the hostname.

It would be nice to have this feature also in RHEL7 to make it easy to upgrade from RHEL6 to RHEL7.
Comment 6 errata-xmlrpc 2018-04-10 13:27:15 EDT
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2018:0936

Note You need to log in before you can comment on or make changes to this bug.