With a client (192.168.1.30) and server, both running v3.1p1, and set to use protocol 2 (in ssh_config on client, and sshd_config on server), Banner does not display. I am using the 2.4.x kernel on both machines. Attached it the output, with verbose mode (-v), from the client. OpenSSH_3.1p1, SSH protocols 1.5/2.0, OpenSSL 0x0090603f debug1: Reading configuration data /usr/local/etc/ssh_config debug1: Applying options for tigger2 debug1: Rhosts Authentication disabled, originating port will not be trusted. debug1: restore_uid debug1: ssh_connect: getuid 500 geteuid 0 anon 1 debug1: Connecting to 192.168.1.1 [192.168.1.1] port 22. debug1: temporarily_use_uid: 500/500 (e=0) debug1: restore_uid debug1: temporarily_use_uid: 500/500 (e=0) debug1: restore_uid debug1: Connection established. debug1: read PEM private key done: type DSA debug1: read PEM private key done: type RSA debug1: identity file /home/guhan/.ssh/identity type 0 debug1: Remote protocol version 1.99, remote software version OpenSSH_3.1p1 debug1: match: OpenSSH_3.1p1 pat OpenSSH* Enabling compatibility mode for protocol 2.0 debug1: Local version string SSH-2.0-OpenSSH_3.1p1 debug1: SSH2_MSG_KEXINIT sent debug1: SSH2_MSG_KEXINIT received debug1: kex: server->client aes128-cbc hmac-md5 none debug1: kex: client->server aes128-cbc hmac-md5 none debug1: SSH2_MSG_KEX_DH_GEX_REQUEST sent debug1: expecting SSH2_MSG_KEX_DH_GEX_GROUP debug1: dh_gen_key: priv key bits set: 115/256 debug1: bits set: 1630/3191 debug1: SSH2_MSG_KEX_DH_GEX_INIT sent debug1: expecting SSH2_MSG_KEX_DH_GEX_REPLY debug1: Host '192.168.1.1' is known and matches the RSA host key. debug1: Found key in /home/guhan/.ssh/known_hosts2:1 debug1: bits set: 1642/3191 debug1: ssh_rsa_verify: signature correct debug1: kex_derive_keys debug1: newkeys: mode 1 debug1: SSH2_MSG_NEWKEYS sent debug1: waiting for SSH2_MSG_NEWKEYS debug1: newkeys: mode 0 debug1: SSH2_MSG_NEWKEYS received debug1: done: ssh_kex2. debug1: send SSH2_MSG_SERVICE_REQUEST debug1: service_accept: ssh-userauth debug1: got SSH2_MSG_SERVICE_ACCEPT debug1: authentications that can continue: publickey,password,keyboard-interactive debug1: next auth method to try is publickey debug1: next auth method to try is keyboard-interactive debug1: authentications that can continue: publickey,password,keyboard-interactive debug1: next auth method to try is password guhan@192.168.1.1's password: Thanks, Wayne Guhan Iyer
You must have Banner set. By default it is commented out. - Ben
Please ignore this bug, I was premature in posting this because later analysis showed my sshd was using the default sshd_config file, i.e. when you run configure with --with-etcdir instead of --sysconfdir, it just ignores the --with-etcdir flag with no warning. And as Ben pointed out, Banner is commented out by default. Hence this was not a bug at all, but rather my (stupid) mistake in running configure.
Mass change of RESOLVED bugs to CLOSED