Your message dated Tue, 18 Feb 2014 20:12:47 +0100
with message-id <1392750767.1657.9.camel@Nokia-N900>
and subject line Closing this bug...
has caused the Debian Bug report #648738,
regarding libssh-4: remmina unable to connect to NX or plain SSH with libsssh-4
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.)
--
648738: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=648738
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: libssh-4
Version: 0.5.2-1
Severity: important
Dear Maintainer,
after the fix for http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=631950
things got worse from the users point of view.
Nor NX nor plain SSH connections are possible. It seems to me that a successful
connection is not regarded as such.
In case of an NX connection attempt:
Remote server logs:
Nov 14 16:43:52 workhorse sshd[26280]: Accepted publickey for nx from
xxx.xxx.xxx.xxx port 53631 ssh2
Nov 14 16:43:52 workhorse sshd[26280]: pam_unix(sshd:session): session opened
for user nx by (uid=0)
Nov 14 16:43:52 workhorse sshd[26287]: fatal: Write failed: Broken pipe
Nov 14 16:43:52 workhorse sshd[26280]: pam_unix(sshd:session): session closed
for user nx
Remmina comes back with an error dialog stating:
"NX SSH authentication failed"
This is in contrast to what the remote machine has logged.
The remmina debug window reveals no information. It stays empty.
In case of a plain SSH connection attempt by password:
Remote server logs:
Nov 14 17:04:09 workhorse sshd[26442]: Accepted password for sg from
xxx.xxx.xxx.xxxport 57010 ssh2
Nov 14 17:04:10 workhorse sshd[26442]: pam_unix(sshd:session): session opened
for user sg by (uid=0)
Nov 14 17:04:10 workhorse sshd[26442]: pam_unix(sshd:session): session closed
for user sg
Remmina comes back with an error dialog stating:
"SSH password authentication failed: Access denied.
Authentication that can continue: publickey,password"
This is in contrast to what the remote machine has logged.
The remmina debug window shows:
[SSH] libssh 0.5.2 (c) 2003-2010 Aris Adamantiadis ([email protected])
Distributed under the LGPL, please refer to COPYING file for information about
your rights, using threading threads_noop
[SSH] Socket connection callback: 1 (0)
[SSH] SSH server banner: SSH-2.0-OpenSSH_5.5p1 Debian-6+squeeze1
[SSH] Analyzing banner: SSH-2.0-OpenSSH_5.5p1 Debian-6+squeeze1
[SSH] We are talking to an OpenSSH client version: 5.5 (50500)
[SSH] Error : Access denied. Authentication that can continue:
publickey,password
In case of a plain SSH connection attempt by public key:
Remote server logs:
Nov 14 17:13:45 workhorse sshd[26537]: Accepted publickey for sg from
xxx.xxx.xxx.xxx port 58512 ssh2
Nov 14 17:13:45 workhorse sshd[26537]: pam_unix(sshd:session): session opened
for user sg by (uid=0)
Nov 14 17:13:45 workhorse sshd[26537]: pam_unix(sshd:session): session closed
for user sg
Remmina comes back with an error dialog stating:
"SSH public key authentication failed: Access denied.
Authentication that can continue: publickey,password"
This is in contrast to what the remote machine has logged.
The remmina debug window shows:
[SSH] libssh 0.5.2 (c) 2003-2010 Aris Adamantiadis ([email protected])
Distributed under the LGPL, please refer to COPYING file for information about
your rights, using threading threads_noop
[SSH] Socket connection callback: 1 (0)
[SSH] SSH server banner: SSH-2.0-OpenSSH_5.5p1 Debian-6+squeeze1
[SSH] Analyzing banner: SSH-2.0-OpenSSH_5.5p1 Debian-6+squeeze1
[SSH] We are talking to an OpenSSH client version: 5.5 (50500)
[SSH] Trying to open /home/sg/.ssh/id_rsa
[SSH] Trying to read /home/sg/.ssh/id_rsa, passphase=true, authcb=false
[SSH] Error : Parsing private key /home/sg/.ssh/id_rsa:
error:06065064:lib(6):func(101):reason(100)
[SSH] Trying to open /home/sg/.ssh/id_rsa
[SSH] Trying to read /home/sg/.ssh/id_rsa, passphase=true, authcb=false
[SSH] Error : Access denied. Authentication that can continue:
publickey,password
Falling back to libssh-4 0.4.8-2 is my current remedy.
Cheers,
Sven
-- System Information:
Debian Release: wheezy/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 3.0.0-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages libssh-4 depends on:
ii libc6 2.13-21
ii libssl1.0.0 1.0.0e-2
ii multiarch-support 2.13-21
ii zlib1g 1:1.2.3.4.dfsg-3
libssh-4 recommends no packages.
libssh-4 suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
Hi,
I have stepped in with supporting Laurent with the libssh package. It seems
that bug 647838 is mostly about a squeeze-bpo of libssh which has been long ago
provided with no further problems reported about remmina.
Thus, closing this bug...
Mike
--
DAS-NETZWERKTEAM
mike gabriel, herweg 7, 24357 fleckeby
fon: +49 (1520) 1976148
GnuPG Key ID 0x25771B13
mail: [email protected], http://das-netzwerkteam.de
--- End Message ---
