為什麼SCP在這種情況下寫入0字節？

我正在嘗試將我的 ssh 密鑰從本地 vm 複製到另一個盒子，一切似乎都正常，但是當我檢查遠端框時，文件不存在……

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

scp 看起來它沒有寫任何東西，但我不知道為什麼！

我想也許是因為內部網路沒有暴露，也許它無法通過 scp 與遠端盒子交談，但它似乎正在做一些握手……當我 scp 到網路中的一個盒子時它工作正常 =/

為什麼 scp 不能在這里工作？

我已經檢查了遠端框的權限看起來沒問題…

沒有錯誤資訊…

scp -v 輸出

[user] > scp -v my.key.pub www@domain.net:.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] > www@domain.net'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。

嘿，FAQ 中甚至還有一個條目：https ://www.complang.tuwien.ac.at/doc/openssh-server/faq.html#2.9

如果您無法傳輸任何文件，這可能是由於您的 .bashrc（或等效項）在非互動式登錄期間（即 rsync’ing、scp’ing 等）做了不應該做的事情；在過去糟糕的日子裡，‘stty’ 因引起此類問題而臭名昭著。請參閱http://theory.uwinnipeg.ca/localfiles/infofiles/bash/bashref_54.html以獲取有關如何檢查您的 shell 是否是互動式的一些提示。

引用自：https://serverfault.com/questions/308660