在这种情况下，SCP为什么要写0字节？

Question

我试图把我的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

Answer 1

那是什么“巴什·斯尔克上膛了”在冗长的输出中？是你的~/..bashrc写的，不是吗？让它消失。

基本上，它与以下内容相同：Rsync似乎与.bashrc不兼容(原因是“您的shell干净了吗？)，但使用scp而不是rsync。

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

Answer 2

如果您无法传输任何文件，这很可能是由于您的.bashrc (或等效的)在非交互登录(即rsync‘in、scp’in等)期间所做的不应该做的事情；在过去糟糕的日子里，'stty‘是特别臭名昭著的，因为它会导致这样的问题。有关如何检查您的shell是否具有交互性的一些提示，请参见http://theory.uwinnipeg.ca/localfiles/infofiles/bash/bashref_54.html。

Answer 3

当应用ssh选项RequestTTY force时，我遇到了这个问题。例如，在我的例子中，我忘记了在我的~/.ssh/config中启用了该选项。

将-o RequestTTY=no添加到scp命令将解决本例中的问题。

有关更多信息，请参见以下答案：https://unix.stackexchange.com/questions/278284/why-does-scp-fail-when-requesttty-force-option-is-enabled