sftp exit debug1: Exit status 255

Belinda Dermody — Mon, 29 Aug 2005 10:12:44 GMT

I have ssh/sftp connections set up between us and several clients. One of the clients has changed machines and I am working with him to get our connection working once again for public key authenication, We get the publickey authenication but a disconnect within seconds. (It is working fine with the other 2, same account and public key). I know it is on his side that is disonnecting after the successful public key. His server is running on a PC and I have
HP-UX_Secure_Shell-A.03.81.002, HP_UX Secure Shell version. I just need to know if anyone has seen the error below and could give me some idea what to tell my client vendor what is wrong. I am googled out a lot of similar problem but no corrective answer.

debug1: Next authentication method: publickey
debug1: Offering public key: /root/.ssh/id_rsa
debug2: we sent a publickey packet, wait for reply
debug1: Server accepts key: pkalg ssh-rsa blen 149
debug2: input_userauth_pk_ok: fp f9:a0:1e:a3:91:85:1f:49:3d:36:c2:c3:31:99:95:36
debug1: read PEM private key done: type RSA
debug1: Authentication succeeded (publickey).
debug1: channel 0: new [client-session]
debug2: channel 0: send open
debug1: Entering interactive session.
debug2: callback start
debug2: ssh_session2_setup: id 0
debug2: channel 0: request pty-req
debug2: channel 0: request shell
debug2: fd 4 setting TCP_NODELAY
debug2: callback done
debug2: channel 0: open confirm rwindow 0 rmax 32768
debug2: channel 0: rcvd adjust 131072
Last login: Mon Aug 29 10:00:40 2005 from chiana.bchp.com
debug2: channel 0: rcvd eof
debug2: channel 0: output open -> drain
debug2: channel 0: obuf empty
debug2: channel 0: close_write
debug2: channel 0: output drain -> closed
debug1: client_input_channel_req: channel 0 rtype exit-status reply 0
debug2: channel 0: rcvd close
debug2: channel 0: close_read
debug2: channel 0: input open -> closed
debug2: channel 0: almost dead
debug2: channel 0: gc: notify user
debug2: channel 0: gc: user detached
debug2: channel 0: send close
debug2: channel 0: is dead
debug2: channel 0: garbage collecting
debug1: channel 0: free: client-session, nchannels 1
Connection to imports.ne16.com closed.
debug1: Transferred: stdin 0, stdout 0, stderr 40 bytes in 1.0 seconds
debug1: Bytes per second: stdin 0.0, stdout 0.0, stderr 41.7
debug1: Exit status 255

Re: sftp exit debug1: Exit status 255

Steven E. Protter — Mon, 29 Aug 2005 10:20:18 GMT

When one of the computers in a public key connection is changed out, public keys must be exchanged anew.

I don't think there is anything else wrong. You might want to be more current on ssh/sftp, but I think the issue is public keys. and maybe entries in the known_hosts files.

SEP

Re: sftp exit debug1: Exit status 255

Belinda Dermody — Mon, 29 Aug 2005 10:26:56 GMT

I already gave him the public keys to process again. But the public key is not the issue because as you can see in the debug publickey authenication was accepted and the connection was made. I also corrected the known host files as stated... The permissions and ownership of the server files are also for the correct client...

Re: sftp exit debug1: Exit status 255

RAC_1 — Mon, 29 Aug 2005 10:28:23 GMT

ssh -vvv

sshd -ddd

Re: sftp exit debug1: Exit status 255

Belinda Dermody — Tue, 30 Aug 2005 08:45:48 GMT

I only had dsa keys created, once I created rsa keys and put the public keys in his authorized_keys file, everything worked correctly. Did not have rsa keys for the first system...

Thanks for the assistance as always.

topic Re: sftp exit debug1: Exit status 255 in Operating System - HP-UX

sftp exit debug1: Exit status 255

Re: sftp exit debug1: Exit status 255

Re: sftp exit debug1: Exit status 255

Re: sftp exit debug1: Exit status 255

Re: sftp exit debug1: Exit status 255