为什么SCP在这种情况下写入0字节?

我试图从我的本地VM复制我的SSH密钥到另一个框,一切似乎工作正常,但是当我检查远程框文件不存在…

Transferred: stdin 0, stdout 0, stderr 0 bytes in 0.0 seconds 

SCP不看它写什么,但我不知道为什么!

我想也许这是因为内部networking没有暴露,也许它不能通过scp与远程框交谈,但它似乎在做一些握手…当我scp到networking中的一个盒子工作正常= /

为什么不会在这里工作?

我已经检查了远程框的权限看起来不错…

没有错误讯息…

scp -v输出

 [user] > scp -v my.key.pub [email protected]:.ssh/ Executing: program /usr/bin/ssh host domain.net, user www, command scp -v -t .ssh/ OpenSSH_4.3p2, OpenSSL 0.9.8e-fips-rhel5 01 Jul 2008 debug1: Reading configuration data /etc/ssh/ssh_config debug1: Applying options for * debug1: Connecting to domain.net [xxx.xxx.xxx.xxx] port 22. debug1: Connection established. debug1: permanently_set_uid: 0/0 debug1: identity file /root/.ssh/identity type -1 debug1: identity file /root/.ssh/id_rsa type -1 debug1: identity file /root/.ssh/id_dsa type -1 debug1: loaded 3 keys debug1: Remote protocol version 2.0, remote software version OpenSSH_5.1p1 Debian-5 debug1: match: OpenSSH_5.1p1 Debian-5 pat OpenSSH* debug1: Enabling compatibility mode for protocol 2.0 debug1: Local version string SSH-2.0-OpenSSH_4.3 debug1: SSH2_MSG_KEXINIT sent debug1: SSH2_MSG_KEXINIT received debug1: kex: server->client aes128-ctr hmac-md5 none debug1: kex: client->server aes128-ctr 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 'domain.net' is known and matches the RSA host key. debug1: Found key in /root/.ssh/known_hosts:11 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 debug1: Next authentication method: publickey debug1: Trying private key: /root/.ssh/identity debug1: Trying private key: /root/.ssh/id_rsa debug1: Trying private key: /root/.ssh/id_dsa debug1: Next authentication method: password [user] > [email protected]'s password: debug1: Authentication succeeded (password). debug1: channel 0: new [client-session] debug1: Entering interactive session. debug1: Sending environment. debug1: Sending env LANG = en_US.UTF-8 debug1: Sending command: scp -v -t .ssh/ Bash Src is loaded! 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 0.0 seconds debug1: Bytes per second: stdin 0.0, stdout 0.0, stderr 0.0 debug1: Exit status 0 

那是什么“Bash Src被加载了!” 在详细输出? 它来自〜/ .bashrc,不是吗? 让它消失。

基本上,这是一样的: Rsync似乎与.bashrc不兼容(导致“你的shell干净?”),但与scp而不是rsync。

嘿,甚至在常见问题中有一个条目: http : //www.openssh.com/faq.html#2.9

如果你无法传输任何文件,这很可能是由于你的.bashrc(或者相当于)在非交互式login时(即rsync,scp等等)所做的。 在过去的糟糕时期,“stty”因为引发这样的问题而尤其臭名昭着。 请参阅http://theory.uwinnipeg.ca/localfiles/infofiles/bash/bashref_54.html关于如何检查你的shell是否交互式的提示&#x3002;