Bug#571606: openssh-client: ssh should write its name when outputting messages
Package: openssh-client
Version: 1:5.3p1-2
Severity: wishlist
ssh outputs messages to the terminal after other processes have
been started on the server side. As ssh doesn't write its name
and it isn't the only process, it may be difficult to know where
messages like that come from.
For instance, I got 12 lines
X11 connection rejected because of wrong authentication.
after the prompt, while I wasn't using the remote machine. The ssh
binary contains such a message, so that I suppose it comes from it
(however I'm not sure as sshd contains it too). So, one should have:
ssh: X11 connection rejected because of wrong authentication.
or
sshd: X11 connection rejected because of wrong authentication.
if this comes from sshd.
-- System Information:
Debian Release: squeeze/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.30-2-amd64 (SMP w/8 CPU cores)
Locale: LANG=POSIX, LC_CTYPE=en_US.ISO8859-1 (charmap=ISO-8859-1)
Shell: /bin/sh linked to /bin/dash
Versions of packages openssh-client depends on:
ii adduser 3.112 add and remove users and groups
ii debconf [debconf-2.0] 1.5.28 Debian configuration management sy
ii dpkg 1.15.5.6 Debian package management system
ii libc6 2.10.2-6 Embedded GNU C Library: Shared lib
ii libedit2 2.11-20080614-1 BSD editline and history libraries
ii libgssapi-krb5-2 1.8+dfsg~alpha1-7 MIT Kerberos runtime libraries - k
ii libssl0.9.8 0.9.8k-8 SSL shared libraries
ii passwd 1:4.1.4.2-1 change and administer password and
ii zlib1g 1:1.2.3.4.dfsg-3 compression library - runtime
Versions of packages openssh-client recommends:
ii openssh-blacklist 0.4.1 list of default blacklisted OpenSS
ii openssh-blacklist-extra 0.4.1 list of non-default blacklisted Op
ii xauth 1:1.0.4-1 X authentication utility
Versions of packages openssh-client suggests:
pn keychain <none> (no description available)
pn libpam-ssh <none> (no description available)
pn ssh-askpass <none> (no description available)
-- no debconf information
Reply to: