[scponly] FreeBSD lost connection
Feargal Reilly
feargal at chrysalink.net
Wed Jun 4 04:46:18 EDT 2003
Hi,
Using scponly-3.8 on FreeBSD 4.8 but it's losing connection and not transferring the file. Initially thought I'd screwed up the chroot stuff, but it happens with the normal scponly too.
I've added an user 'test', set shell to /usr/local/bin/scponly, created homedir /home/test, chown'ed to test, set password.
Added /usr/local/bin/scponly to /etc/shells, although I don't think it makes a difference.
When trying to scp a file to the server, I get an error 'connection lost'
Here's the output when I try:
ttyp0> scp -v foo test at localhost:
Executing: program /usr/bin/ssh host localhost, user test, command scp -v -t .
OpenSSH_3.5p1 FreeBSD-20030201, SSH protocols 1.5/2.0, OpenSSL 0x0090701f
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: Rhosts Authentication disabled, originating port will not be trusted.
debug1: ssh_connect: needpriv 0
debug1: Connecting to localhost [127.0.0.1] port 22.
debug1: Connection established.
debug1: identity file /home/feargal/.ssh/identity type -1
debug1: identity file /home/feargal/.ssh/id_rsa type -1
debug1: identity file /home/feargal/.ssh/id_dsa type -1
debug1: Remote protocol version 1.99, remote software version OpenSSH_3.5p1 FreeBSD-20030201
debug1: match: OpenSSH_3.5p1 FreeBSD-20030201 pat OpenSSH*
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_3.5p1 FreeBSD-20030201
debug1: SSH2_MSG_KEXINIT sent
debug1: SSH2_MSG_KEXINIT received
debug1: kex: server->client aes128-cbc hmac-md5 none
debug1: kex: client->server aes128-cbc hmac-md5 none
debug1: SSH2_MSG_KEX_DH_GEX_REQUEST sent
debug1: expecting SSH2_MSG_KEX_DH_GEX_GROUP
debug1: dh_gen_key: priv key bits set: 127/256
debug1: bits set: 1645/3191
debug1: SSH2_MSG_KEX_DH_GEX_INIT sent
debug1: expecting SSH2_MSG_KEX_DH_GEX_REPLY
debug1: Host 'localhost' is known and matches the DSA host key.
debug1: Found key in /home/feargal/.ssh/known_hosts:2
debug1: bits set: 1617/3191
debug1: ssh_dss_verify: signature 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
debug1: authentications that can continue: publickey,password,keyboard-interactive
debug1: next auth method to try is publickey
debug1: try privkey: /home/feargal/.ssh/identity
debug1: try privkey: /home/feargal/.ssh/id_rsa
debug1: try privkey: /home/feargal/.ssh/id_dsa
debug1: next auth method to try is keyboard-interactive
Password:
debug1: authentications that can continue: publickey,password,keyboard-interactive
Password:
debug1: ssh-userauth2 successful: method keyboard-interactive
debug1: fd 4 setting O_NONBLOCK
debug1: fd 5 setting O_NONBLOCK
debug1: channel 0: new [client-session]
debug1: send channel open 0
debug1: Entering interactive session.
debug1: ssh_session2_setup: id 0
debug1: Sending command: scp -v -t .
debug1: channel request 0: exec
debug1: channel 0: open confirm rwindow 0 rmax 32768
debug1: client_input_channel_req: channel 0 rtype exit-status reply 0
debug1: channel 0: rcvd eof
debug1: channel 0: output open -> drain
debug1: channel 0: obuf empty
debug1: channel 0: close_write
debug1: channel 0: output drain -> closed
debug1: channel 0: rcvd close
debug1: channel 0: close_read
debug1: channel 0: input open -> closed
debug1: channel 0: almost dead
debug1: channel 0: gc: notify user
debug1: channel 0: gc: user detached
debug1: channel 0: send close
debug1: channel 0: is dead
debug1: channel 0: garbage collecting
debug1: channel_free: channel 0: client-session, nchannels 1
debug1: fd 0 clearing O_NONBLOCK
debug1: fd 1 clearing O_NONBLOCK
debug1: Transferred: stdin 0, stdout 0, stderr 0 bytes in 0.1 seconds
debug1: Bytes per second: stdin 0.0, stdout 0.0, stderr 0.0
debug1: Exit status 1
lost connection
If I change his shell to /bin/sh it works perfectly, so it is a problem with scponly. Has anybody else seen this? Is there any more info I can provide to track this down?
Thanks,
-Feargal.
--
Feargal Reilly,
Codeshifter,
Chrysalink Systems.
More information about the scponly
mailing list