openssh unix dev - Jan 2004 - openssh-unix-dev Digest, Vol 9, Issue 16

On Solaris, if you create a banner file /etc/issue it will do what I 
think you want. However, it comes in on stderr from your ssh client, so 
you need to do complicated things to get clean output from stderr of 
remote commands.

Does anyone know if this is different from the banner option in the 
sshd_config that everyone's been talking about?

On Jan 15, 2004, at 7:13 PM, openssh-unix-dev-request at mindrot.org wrote:
> Message: 1
> Date: Wed, 14 Jan 2004 16:21:45 -0200
> From: Glauco Marolla <Glauco.Marolla at Sun.COM>
> Subject: Banner doubts
> To: openssh-unix-dev at mindrot.org
> Message-ID: <400588B9.C7064B18 at sun.com>
> Content-Type: text/plain; charset=us-ascii
>
> Hi all. I'd like to know if someone knows how to implement  a banner 
> to be prompted just after a connection to a server is initialized. 
> It's necessary doing that to warm who is trying to access the server 
> just for security.
>
> Regards,
>
> 	Glauco
>
---
Jeremy McMillan

Jeremy McMillan wrote:
> On Solaris, if you create a banner file /etc/issue it will do what I 
> think you want. However, it comes in on stderr from your ssh client, so 
> you need to do complicated things to get clean output from stderr of 
> remote commands.
> 
> Does anyone know if this is different from the banner option in the 
> sshd_config that everyone's been talking about?
The /etc/issue file is used by Solaris' own services (eg login).  The 
Banner directive is used by sshd to send the contents of the specified 
file to the client for display.

You can use the same file for both purposes (ie put "Banner
/etc/issue"
into sshd_config) or you can use a different file to send a different 
message to ssh users.

-- 
Darren Tucker (dtucker at zip.com.au)
GPG key 8FF4FA69 / D9A3 86E9 7EEE AF4B B2D4  37C9 C982 80C7 8FF4 FA69
     Good judgement comes with experience. Unfortunately, the experience
usually comes from bad judgement.