- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: Warning banner from /etc/issue is not displayi...
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Discussions
Forums
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-02-2013 11:38 PM
тАО12-02-2013 11:38 PM
Dears
I'm not able to view the contents of /etc/issue file. When login via SSH.
IтАЩve edited the /etc/inetd.conf as
telnet stream tcp6 nowait root /usr/lbin/telnetd telnetd -b /etc/issue
login stream tcp6 nowait root /usr/lbin/rlogind rlogind -B /etc/issue
#inetd -c
#restarted the SSH demon
But Banner is not displaying before I loginтАж Please helpтАж
Regards,
Pranay
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-03-2013 12:55 AM
тАО12-03-2013 12:55 AM
SolutionThe sshd daemon does not read /etc/inetd.conf at all. The settings you've added will affect incoming logins using the telnet and rlogin protocols only. Local console logins will also display /etc/issue if it exists.
You should add this line to the sshd configuration file (usually /opt/ssh/etc/sshd_config):
Banner /etc/issue
Then restart the sshd daemon.
Note: only SSH protocol version 2 can display pre-login banners. Since SSH protocol version 1 is old and has known weaknesses, you should only allow SSH protocol version 2 anyway. So make sure that your sshd configuration file also has this line:
Protocol 2
If the Protocol line says "Protocol 2,1" or "Protocol 1,2", change it to "Protocol 2" only.
- Tags:
- sshd
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-03-2013 03:44 AM
тАО12-03-2013 03:44 AM
Re: Warning banner from /etc/issue is not displaying via SSH.
Now it is working when i changed the Protocol 2 only :) :)
Regards,
Pranay
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-17-2013 08:34 PM
тАО12-17-2013 08:34 PM
Re: Warning banner from /etc/issue is not displaying via SSH.
Dear MK,
In few servers i'm not able to get the warning banner after doing the configuration. What could be the reason?
regards,
Pranay
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-18-2013 05:48 AM
тАО12-18-2013 05:48 AM
Re: Warning banner from /etc/issue is not displaying via SSH.
Did you restart sshd after changing the configuration?
My suggestions assumed that you're using a reasonably modern version of the free HP SSH package. If your server is running a commercial SSH package, its configuration file might be elsewhere and might use a different syntax.
A very old version of sshd might not support the necessary configuration keywords. In that case, there should be a message in the syslog about sshd detecting an unknown keyword in the configuration.
If there is a SSH proxy between you and the actual host (e.g. for logging purposes, or someone is being malicious), then it might be filtering what you actually see.