Your message dated Thu, 28 Nov 2024 18:21:16 +0000
with message-id <[email protected]>
and subject line Bug#1085868: Removed package(s) from unstable
has caused the Debian Bug report #721837,
regarding monkeysphere ssh-proxycommand fails if error in known_hosts file
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
721837: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=721837
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: monkeysphere
Version: 0.36-1
Severity: normal
Dear Maintainer,
I had a hard time debugging a disturbing and seemingly intermittent
failure while using the monkeysphere . When trying to connect to a small
subset of the servers I usually connect to, I immediately got a
connection refused error from ssh, before I even started connecting to
the remote server.
When disabling the monkeysphere-proxycommand in ~/.ssh/config I was able
to successfully connect to these hosts.
After much hand-wringing and debugging, I tried calling:
MONKEYSPHERE_LOG_LEVEL=DEBUG /usr/bin/monkeysphere ssh-proxycommand <host>
With working hosts, we get an SSH welcome message. With the non-working
hosts I received no feedback and exit code 1.
I finally tracked it down:
ssh-keygen -F <host> -f /home/jamie/.ssh/known_hosts
Which generated a useful error about my known_hosts file having a line
that was too long (somehow I had inserted garbage into my known_hosts
file which prevent ssh-keygen from working properly).
So, the small subset of hosts that were failing were the ones that
weren't in my OpenPGP keyring (which makes sense ... mostly this was
affecting my access to the non-public virtual guests on my laptop.).
I *think* the proper fixes are:
* Check the error code when calling ssh-keygen and return a reasonable
error to the user if it fails.
* Add more feedback to the ssh-proxycommand subcommand when
MONKEYSPHERE_LOG_LEVEL=DEBUG
jamie (sjj)
-- System Information:
Debian Release: jessie/sid
APT prefers testing
APT policy: (500, 'testing'), (200, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.10-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages monkeysphere depends on:
ii adduser 3.113+nmu3
ii gnupg 1.4.14-1
ii libcrypt-openssl-rsa-perl 0.28-1
ii lockfile-progs 0.1.17
ii perl [libdigest-sha-perl] 5.14.2-21
Versions of packages monkeysphere recommends:
ii cron 3.0pl1-124
ii netcat-traditional [netcat] 1.10-40
ii openssh-client 1:6.2p2-6
ii socat 1.7.2.2-1
ii ssh-askpass 1:1.2.4.1-9
Versions of packages monkeysphere suggests:
ii msva-perl [monkeysphere-validation-agent] 0.9.1-1
-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 0.43-3.1+rm
Dear submitter,
as the package monkeysphere has just been removed from the Debian archive
unstable we hereby close the associated bug reports. We are sorry
that we couldn't deal with your issue properly.
For details on the removal, please see https://bugs.debian.org/1085868
The version of this package that was in Debian prior to this removal
can still be found using https://snapshot.debian.org/.
Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.
This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
[email protected].
Debian distribution maintenance software
pp.
Thorsten Alteholz (the ftpmaster behind the curtain)
--- End Message ---
