search for: ssh2_msg_service_accept

...gnature 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 Any ideas what's going wrong here, or are there any better diagnostics I could supply to the list to help track this down? thanks, - -- Matthew Bloch Bytemark Hosting tel. +44 (0) 8707 455026 http://www.by...

...ssh there is a long delay before I get the password prompt. I ran ssh -v and I found that it gets up to this: debug1: ssh_ecdsa_verify: signature correct debug1: SSH2_MSG_NEWKEYS sent debug1: expecting SSH2_MSG_NEWKEYS debug1: SSH2_MSG_NEWKEYS received debug1: SSH2_MSG_SERVICE_REQUEST sent debug1: SSH2_MSG_SERVICE_ACCEPT received and then it sits there for 1-2 minutes and then this output blasts out: debug1: Authentications that can continue: publickey,gssapi-keyex,gssapi-with-mic,password debug1: Next authentication method: gssapi-keyex debug1: No valid Key exchange context debug1: Next authentication method: gs...

Hi! I am distributing 2.5.1p1 for production use on my system by now and prepare switching to protocol 2 as default protocol. I just noted, that ssh-agent can be used for protocol 1 and 2, but the keys kept in ssh-agent are not compared against keys in .ssh. Example: I have a DSA key in id_dsa which I load into ssh-agent on login. When connecting to an account accepting the key everything is

...len 40 datafellows 15 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: buggy server: service_accept w/o service debug: got SSH2_MSG_SERVICE_ACCEPT debug: authentications that can continue: Permission denied (). debug: Calling cleanup 0x805ba68(0x0) [gleblanc at grego1 gleblanc]$

...g1: ssh_rsa_verify: signature correct debug2: kex_derive_keys debug2: set_newkeys: mode 1 debug1: SSH2_MSG_NEWKEYS sent debug1: expecting SSH2_MSG_NEWKEYS debug2: set_newkeys: mode 0 debug1: SSH2_MSG_NEWKEYS received debug1: SSH2_MSG_SERVICE_REQUEST sent debug2: service_accept: ssh-userauth debug1: SSH2_MSG_SERVICE_ACCEPT received debug1: Authentications that can continue: publickey,password debug3: start over, passed a different list publickey,password debug3: preferred publickey,password debug3: authmethod_lookup publickey debug3: remaining preferred: password debug3: authmethod_is_enabled publickey debug1: Next a...

...problems with anoncvs.mindrot.org? I do a cvs update on a semi-regular basis and it has been failing for the past few days. $ cvs up Connection closed by 116.66.166.109 cvs [update aborted]: end of file from server (consult above messages if any) $ It looks like ssh gets to the point of receiving SSH2_MSG_SERVICE_ACCEPT and then the connection is closed. I'm wondering if this might be a side-effect of bz#1638. Regards, -- Iain Morgan

Hi, Can somebody explain what is the hex string following the path to the RSA key used for authentication? For an example, see last line in the debug snippet shown below. debug1: SSH2_MSG_SERVICE_REQUEST sent debug2: service_accept: ssh-userauth debug1: SSH2_MSG_SERVICE_ACCEPT received debug2: key: /Users/blah/.ssh/id_rsa (0x6fef81c1d114) How is that value generated? Is it something I can also do from the command line? First, I thought it is the fingerprint of the public key (as in ssh-keygen -l), but that's not it. Regards, Dragos

...to use a special key "specialkey" to log in to a particular server (which has MaxAuthTries=3): $ ssh -i specialkey joe at ssh.example.com ... debug1: SSH2_MSG_NEWKEYS sent debug1: expecting SSH2_MSG_NEWKEYS debug1: SSH2_MSG_NEWKEYS received debug1: SSH2_MSG_SERVICE_REQUEST sent debug1: SSH2_MSG_SERVICE_ACCEPT received debug1: Authentications that can continue: publickey debug1: Next authentication method: publickey debug1: Offering public key: key1 debug1: Authentications that can continue: publickey debug1: Offering public key: key2 debug1: Authentications that can continue: publickey debug1: Offering...

...ebug1: newkeys: mode 1 debug1: Enabling compression at level 6. 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 debug3: start over, passed a different list publickey,password,keyboard-interactive debug3: preferred publickey,keyboard-interactive,password debug3: authmethod_lookup publickey debug3: remaining preferred: keyboard-...

...t our people in diagnosing "why is it always asking me for passwords"). All clients and servers are 3.0p1. First: server does not have the client's RSA2 key in known_host. 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,hostbased debug1: next auth method to try is hostbased debug1: Remote: Accepted by .shosts. debug1: authentications that can continue: publickey,password,keyboard-interactive,hostbased debug1: Remote: Accepted by .sh...

Out of the box on Solaris 2.7 using the internal entropy system. I am able to login but as soon as I get past the password prompt it dies because it claims the RNG is not initialised. Transcript: [..] debug: got SSH2_MSG_SERVICE_ACCEPT You have entered the land of dragons and mystical creatures. This server does not exist. debug: authentications that can continue: publickey,keyboard-interactive,password debug: ne...

Hi, I'm using 2-factor authentication (pubkey+googe_authenticator) and have an issue with rsync. It's configured to use pubkey to authenticate to server so when google_authentication is bypassed by not creating .google_authenticator file for particular user (thanks to nullok option in PAM) it still sends to stderr "Authenticated with partial success." message although it

...ails near the end like this: . . . 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: kerberos-tgt-2 at ssh.com,kerberos-1 at ssh.com,password,hostbased debug1: no more auth methods to try Permission denied (kerberos-tgt-2 at ssh.com,kerberos-1 at ssh.com,password,hostbased). debug1: Calling cleanup 0x80641a4(0x0) I've put Kerberos...

I think I had better update akk the kerberos and gssapi to the latest? Please advise. Thanks Tedc ssh -vvv admin at geronimo.creedon.biz <<<<<<<<snip>>>>>>>>> debug2: service_accept: ssh-userauth debug1: SSH2_MSG_SERVICE_ACCEPT received debug2: key: /root/.ssh/identity ((nil)) debug2: key: /root/.ssh/id_rsa (0x568da0) debug2: key: /root/.ssh/id_dsa (0x568dc0) debug1: Authentications that can continue: gssapi-with-mic debug3: start over, passed a different list gssapi-with-mic debug3: preferred gssapi-with-mic debug3: auth...

Hai, Lets start here. Handy for us to know. OS? Samba version? AD or member setup? And I suggest, set this in the ssh server. # GSSAPI options GSSAPIAuthentication yes Restart the ssh server and try to SSO login. If its a AD server this should work. Yes, you dont get home dir etc, end up in / after login, but lets check if this works. Greetz, Louis > -----Oorspronkelijk

...instead of ASCII (which breaks RFC 4253) and I am not sure how to do the conversion properly so that it will not corrupt truely binary data. The second problem is that connection fails even for ssh client and deamon that belong to the same build. Here is the output of sshd (the client has received SSH2_MSG_SERVICE_ACCEPT and is running dispatch_run): debug1: attempt 0 failures 0 debug3: mm_getpwnamallow entering debug3: mm_request_send entering: type 6 debug3: mm_getpwnamallow: waiting for MONITOR_ANS_PWNAM debug3: mm_request_receive_expect entering: type 7 debug3: mm_request_receive entering debug3: monitor_read:...

...e ECDSA host key. debug1: Found key in /home/knoppix/.ssh/known_hosts:29 debug1: ssh_ecdsa_verify: signature correct debug1: SSH2_MSG_NEWKEYS sent debug1: expecting SSH2_MSG_NEWKEYS debug1: SSH2_MSG_NEWKEYS received debug1: Roaming not allowed by server debug1: SSH2_MSG_SERVICE_REQUEST sent debug1: SSH2_MSG_SERVICE_ACCEPT received debug1: Authentications that can continue: publickey,password debug1: Next authentication method: publickey debug1: Trying private key: /home/knoppix/.ssh/id_rsa debug1: Trying private key: /home/knoppix/.ssh/id_dsa debug1: Trying private key: /home/knoppix/.ssh/id_ecdsa debug1: Next authe...

...8.2.226 port 34813 ssh2 Connection closed by 192.168.2.226 debug1: Calling cleanup 0x22fcc(0x0) debug1: Calling cleanup 0x3c848(0x0) ********************* Error message generated from the client-side command (as the target user) ssh -F /usr/local/etc/ssh_config -p 1024 -v -v -v NFS debug1: got SSH2_MSG_SERVICE_ACCEPT debug1: authentications that can continue: keyboard-interactive,hostbased debug3: start over, passed a different list keyboard-interactive,hostbased debug3: preferred hostbased,password debug3: authmethod_lookup hostbased debug3: remaining preferred: password debug3: authmethod_is_enabled hostbased...

...s the RSA host key. debug1: Found key in /home/swinchen/.ssh/known_hosts:1 debug1: ssh_rsa_verify: signature correct debug1: SSH2_MSG_NEWKEYS sent debug1: expecting SSH2_MSG_NEWKEYS debug1: SSH2_MSG_NEWKEYS received debug1: Roaming not allowed by server debug1: SSH2_MSG_SERVICE_REQUEST sent debug1: SSH2_MSG_SERVICE_ACCEPT received debug1: Authentications that can continue: publickey debug1: Next authentication method: publickey debug1: Trying private key: /home/swinchen/.ssh/id_rsa debug1: PEM_read_PrivateKey failed debug1: read PEM private key done: type <unknown> Enter passphrase for key '/home/swinchen/...

...juniper.net' is known and matches the DSA host key. debug1: Found key in /homes/rodrigc/.ssh/known_hosts:100 debug1: ssh_dss_verify: signature correct debug1: SSH2_MSG_NEWKEYS sent debug1: expecting SSH2_MSG_NEWKEYS debug1: SSH2_MSG_NEWKEYS received debug1: SSH2_MSG_SERVICE_REQUEST sent debug1: SSH2_MSG_SERVICE_ACCEPT received xmalloc: zero size At this point I cannot log in. The system I am trying to log into is: 4.11-RELEASE-p26 Any ideas? This is a big problem for me, because I have a lot of FreeBSD 4.x servers that I need to log into. Thanks. -- Craig Rodrigues rodrigc@crodrigues.org