SCP problem

Lotharster · 11-30-2005, 04:47 PM

I think scp is behaving in a funny way, but probably it's just me. So please tell me why this command does not work:

Code:

scp test plutonium:/home/ltmp/

I run this command in my home directory, test is a file in that home directory.
plutonium is another machine in the same network, logon via ssh works fine (btw, I'm using ssh-agent for authentification).
My username is the same on both machines.

What am I doing wrong?

PS: I executed the command with the -v option, and it gave me this:

Code:

eisen:~$ scp -v test plutonium:/home/ltmp/
Executing: program /usr/bin/ssh host plutonium, user (unspecified), command scp-v -t /home/ltmp/
OpenSSH_3.8.1p1 Debian-8.sarge.4, OpenSSL 0.9.7e 25 Oct 2004
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: Connecting to plutonium [137.250.83.64] port 22.
debug1: Connection established.
debug1: identity file /.../dce.uni-augsburg.de/fs/home/physik/exp1/schmidlo/.ssh/identity type -1
debug1: identity file /.../dce.uni-augsburg.de/fs/home/physik/exp1/schmidlo/.ssh/id_rsa type -1
debug1: identity file /.../dce.uni-augsburg.de/fs/home/physik/exp1/schmidlo/.ssh/id_dsa type -1
debug1: Remote protocol version 2.0, remote software version OpenSSH_3.8.1p1 Debian-8.sarge.4
debug1: match: OpenSSH_3.8.1p1 Debian-8.sarge.4 pat OpenSSH*
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_3.8.1p1 Debian-8.sarge.4
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(1024<1024<8192) sent
debug1: expecting SSH2_MSG_KEX_DH_GEX_GROUP
debug1: SSH2_MSG_KEX_DH_GEX_INIT sent
debug1: expecting SSH2_MSG_KEX_DH_GEX_REPLY
debug1: Host 'plutonium' is known and matches the RSA host key.
debug1: Found key in /.../dce.uni-augsburg.de/fs/home/physik/exp1/schmidlo/.ssh/known_hosts:5
debug1: ssh_rsa_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
debug1: Authentications that can continue: publickey,password,keyboard-interactive
debug1: Next authentication method: publickey
debug1: Offering public key: .ssh/id_schmidlo
debug1: Server accepts key: pkalg ssh-dss blen 817
debug1: Authentication succeeded (publickey).
debug1: channel 0: new [client-session]
debug1: Entering interactive session.
debug1: Sending command: scp -v -t /home/ltmp/
Willkommen!
eisen:~$ debug1: client_input_channel_req: channel 0 rtype exit-status reply 0
debug1: channel 0: free: 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 5.1 seconds
debug1: Bytes per second: stdin 0.0, stdout 0.0, stderr 0.0
debug1: Exit status 0

Lotharster · 11-30-2005, 05:06 PM

I realized that if I remove my .bashrc file, scp works just fine. But what is the problem with my bashrc?
Here it is:

Code:

if [ $HOSTNAME = eisen ]
then
 echo Willkommen auf eisen!
 . ~/scripte/ssh_agent
else
 echo Willkommen!
fi

~
~
~

ssfrstlstnm · 11-30-2005, 05:28 PM

I think this is the problem

Code:

 . ~/scripte/ssh_agent

I'm not sure why, but if it works without your bashrc file. Then you may as well remove this line. You only need ssh-client and ssh-server. What does the script ssh-agent do?

Lotharster · 11-30-2005, 05:45 PM

The agent is not the problem. It handles the authentification so that I don't need to type in the password everytime I use ssh. I need it for using scp in scripts.

The real problem are the "echo"-commands. No Idea why, but when I outcomment them, scp works. If you have any idea why that is so, tell me.

EDIT: typos

ssfrstlstnm · 12-01-2005, 07:42 AM

I don't know why either. Maybe try putting quotes around the string being echoed?

spooon · 12-01-2005, 03:41 PM

Quote:

Originally posted by Lotharster
The agent is not the problem. It handles the authentification so that I don't need to type in the password everytime I use ssh. I need it for using scp in scripts.

I think the usual way of logging in without passwords is by using public-key authentication; by doing ssh-keygen on the client to make a key, and then adding that to the .ssh/authorized_keys2 file on the server.

Lotharster · 12-02-2005, 03:40 AM

Quote:

Originally posted by spooon
I think the usual way of logging in without passwords is by using public-key authentication; by doing ssh-keygen on the client to make a key, and then adding that to the .ssh/authorized_keys2 file on the server.

That's exactly what I'm doing. The ssh_agent-script sets the environment variables so that ssh-agent can handle the authentification process.