When trying to log in from a suse 8.0 with following ssh version:
SSH Version OpenSSH_2.3.0p1, protocol versions 1.5/2.0.
Compiled with SSL (0x0090600f).

into a freshly installed debian sarge with:
OpenSSH_3.8.1p1 Debian-8.sarge.4, OpenSSL 0.9.7e 25 Oct 2004

i get this message:
Unable to find an authentication method

No password asked, no login possible.

Other distro/ssh can correctly log into that machine.
And the first machine can log in into other pc's.
Only the a/m combination gets that error.

Could it be a v.1/v.2 ssh protocol issue ? Or a cypher mechanism issue ?

Any idea/tip appreciated.
--
Post prandium stabis, post coenam ambulabis.

RRB

On Tue, 11 Jan 2005 13:06:40 +0100, RRB
<rrb@despammed.com> wrote:
> Other distro/ssh can correctly log into that machine.
> And the first machine can log in into other pc's.
> Only the a/m combination gets that error.
>
> Could it be a v.1/v.2 ssh protocol issue ? Or a cypher mechanism issue ?
>
> Any idea/tip appreciated.

ssh -v

--
BOFH excuse #270:

Someone has messed up the kernel pointers

Bill Marcum wrote:
> On Tue, 11 Jan 2005 13:06:40 +0100, RRB
> <rrb@despammed.com> wrote:
>
>>Other distro/ssh can correctly log into that machine.
>>And the first machine can log in into other pc's.
>>Only the a/m combination gets that error.
>>
>>Could it be a v.1/v.2 ssh protocol issue ? Or a cypher mechanism issue ?
>>
>>Any idea/tip appreciated.
>
>
> ssh -v
>

I did it, but as i never experienced similar error i could not make very much
(ehm..nothing) with that.
Goggling was also not very helpful...

If you like and can help i may post it for you.

--
Post prandium stabis, post coenam ambulabis.

RRB

Bill Marcum wrote:
> On Tue, 11 Jan 2005 13:06:40 +0100, RRB
> <rrb@despammed.com> wrote:
>
>>Other distro/ssh can correctly log into that machine.
>>And the first machine can log in into other pc's.
>>Only the a/m combination gets that error.
>>
>>Could it be a v.1/v.2 ssh protocol issue ? Or a cypher mechanism issue ?
>>
>>Any idea/tip appreciated.
>
>
> ssh -v
here it is.

>
SSH Version OpenSSH_2.3.0p1, protocol versions 1.5/2.0.
Compiled with SSL (0x0090600f).
debug: Reading configuration data /etc/ssh/ssh_config
debug: Seeding random number generator
debug: ssh_connect: getuid 502 geteuid 0 anon 0
debug: Connecting to a_server [192.168.1.10] port 22.
debug: Allocated local port 1023.
debug: Connection established.
debug: Remote protocol version 2.0, remote software version OpenSSH_3.8.1p1
Debian-8.sarge.4
debug: no match: OpenSSH_3.8.1p1 Debian-8.sarge.4
Enabling compatibility mode for protocol 2.0
debug: Local version string SSH-2.0-OpenSSH_2.3.0p1
debug: Seeding random number generator
debug: send KEXINIT
debug: done
debug: wait KEXINIT
debug: got kexinit: diffie-hellman-group-exchange-sha1,diffie-hellman-group1-sha1
debug: got kexinit: ssh-rsa,ssh-dss
debug: got kexinit:
3des-cbc,blowfish-cbc,cast128-cbc,arcfour,rijndael-cbc@lysator.liu.se
debug: got kexinit:
3des-cbc,blowfish-cbc,cast128-cbc,arcfour,rijndael-cbc@lysator.liu.se
debug: got kexinit:
hmac-md5,hmac-sha1,hmac-ripemd160,hmac-ripemd160@openssh.com,hmac-sha1-96,hmac-md5-96
debug: got kexinit:
hmac-md5,hmac-sha1,hmac-ripemd160,hmac-ripemd160@openssh.com,hmac-sha1-96,hmac-md5-96
debug: got kexinit: none,zlib
debug: got kexinit: none,zlib
debug: got kexinit:
debug: got kexinit:
debug: first kex follow: 0
debug: reserved: 0
debug: done
debug: kex: server->client 3des-cbc hmac-sha1 none
debug: kex: client->server 3des-cbc hmac-sha1 none
debug: Sending SSH2_MSG_KEX_DH_GEX_REQUEST.
debug: Wait SSH2_MSG_KEX_DH_GEX_GROUP.
debug: Got SSH2_MSG_KEX_DH_GEX_GROUP.
debug: bits set: 2042/4096
debug: Sending SSH2_MSG_KEX_DH_GEX_INIT.
debug: Wait SSH2_MSG_KEX_DH_GEX_REPLY.
debug: Got SSH2_MSG_KEXDH_REPLY.
debug: Host 'a_server' is known and matches the DSA host key.
debug: bits set: 2010/4096
debug: len 55 datafellows 0
debug: dsa_verify: signature correct
debug: Wait SSH2_MSG_NEWKEYS.
debug: GOT SSH2_MSG_NEWKEYS.
debug: send SSH2_MSG_NEWKEYS.
debug: done: send SSH2_MSG_NEWKEYS.
debug: done: KEX2.
debug: send SSH2_MSG_SERVICE_REQUEST
debug: service_accept: ssh-userauth
debug: got SSH2_MSG_SERVICE_ACCEPT
debug: authentications that can continue: publickey,keyboard-interactive
debug: next auth method to try is publickey
debug: key does not exist: /home/paolo/.ssh/id_dsa
debug: no more auth methods to try
Unable to find an authentication method
debug: Calling cleanup 0x80608e0(0x0)

--
Frau Blucher! iiiihhhhiiiihihihiihiihihihihhhh!!!

RRB

In article <41e46b03$0$130$5fc30a8@news.tiscali.it>,
RRB <rrb@despammed.com> wrote:

>debug: authentications that can continue: publickey,keyboard-interactive

"password" is missing from this list. If you want to enable password
authentication, make sure your server's /etc/ssh/sshd_config has a
"PasswordAuthentication yes" line.

Lawrence D'Oliveiro wrote:
> In article <41e46b03$0$130$5fc30a8@news.tiscali.it>,
> RRB <rrb@despammed.com> wrote:
>
>
>>debug: authentications that can continue: publickey,keyboard-interactive
>
>
> "password" is missing from this list. If you want to enable password
> authentication, make sure your server's /etc/ssh/sshd_config has a
> "PasswordAuthentication yes" line.

I did it and it works. Thank you very much.

The strange thing is that another host with the same distro was able to log
in.... that confused me...

--
"... punto, due punti! Vai, fai vedere che abbondiamo... adbondantis adbondantum..."

RRB

In article <41e4f6ab$0$129$5fc30a8@news.tiscali.it>,
RRB <rrb@despammed.com> wrote:

>Lawrence D'Oliveiro wrote:
>> In article <41e46b03$0$130$5fc30a8@news.tiscali.it>,
>> RRB <rrb@despammed.com> wrote:
>>
>>>debug: authentications that can continue: publickey,keyboard-interactive
>>
>> "password" is missing from this list. If you want to enable password
>> authentication, make sure your server's /etc/ssh/sshd_config has a
>> "PasswordAuthentication yes" line.
>
>I did it and it works. Thank you very much.
>
>The strange thing is that another host with the same distro was able to log
>in.... that confused me...

Maybe it was using the "keyboard-interactive" option (not that I
understand exactly how that works). Or had you previously set up a key
pair to use with the "publickey" option?

Lawrence D'Oliveiro wrote:
....
>>>>debug: authentications that can continue: publickey,keyboard-interactive
>>>
>>>"password" is missing from this list. If you want to enable password
>>>authentication, make sure your server's /etc/ssh/sshd_config has a
>>>"PasswordAuthentication yes" line.
>>
>>I did it and it works. Thank you very much.
>>
>>The strange thing is that another host with the same distro was able to log
>>in.... that confused me...
>
>
> Maybe it was using the "keyboard-interactive" option (not that I
> understand exactly how that works). Or had you previously set up a key
> pair to use with the "publickey" option?

I don't know exactly, i will investigate a little.
The thing happened after a reinstall of the pc that runs the sshd server, all
the clients was to be cleaned the .ssh/known_hosts file and everything went
fine, only that one host could not authenticate.
If i discover something i'll post it.

--
Post prandium stabis, post coenam ambulabis.

RRB