问题描述
我有两个用户在Fedora中:
I have two users in Fedora:
(ⅰ)迩
(二)根(相当明显!)
(i) Wani(ii) root (quite obvious!)
我的用户迩的.bashrc中的内容是:
My contents of .bashrc of user Wani are:
# .bashrc
echo "Hello"
# Source global definitions
if [ -f /etc/bashrc ]; then
. /etc/bashrc
fi
# User specific aliases and functions
现在登录到根后,我键入以下命令:
Now after logging into root, I type the following commands:
[root@Dell Wani]#touch try.txt
[root@Dell Wani]#service sshd start
[root@Dell Wani]#scp try.txt Wani@localhost:~/
Wani@localhost's password:
Hello
[root@Dell Wani]#
现在我登录到迩,然后键入:
Now I log into Wani, and type:
[Wani@Dell ~]$ cat try.txt
cat: try.txt: No such file or directory
[Wani@Dell ~]$
现在我再次登录到根和-v键入相同的命令:
Now I again log into root and type the same command with -v:
[root@Dell Wani]# scp -v morph.log Wani@localhost:
Executing: program /usr/bin/ssh host localhost, user Wani, command scp -v -t -- .
OpenSSH_5.6p1, OpenSSL 1.0.0j-fips 10 May 2012
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: Applying options for *
debug1: Connecting to localhost [127.0.0.1] port 22.
debug1: Connection established.
debug1: permanently_set_uid: 0/0
debug1: identity file /root/.ssh/id_rsa type -1
debug1: identity file /root/.ssh/id_rsa-cert type -1
debug1: identity file /root/.ssh/id_dsa type -1
debug1: identity file /root/.ssh/id_dsa-cert type -1
debug1: Remote protocol version 2.0, remote software version OpenSSH_5.6
debug1: match: OpenSSH_5.6 pat OpenSSH*
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_5.6
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 'localhost' is known and matches the RSA host key.
debug1: Found key in /root/.ssh/known_hosts:2
debug1: ssh_rsa_verify: signature correct
debug1: SSH2_MSG_NEWKEYS sent
debug1: expecting SSH2_MSG_NEWKEYS
debug1: SSH2_MSG_NEWKEYS received
debug1: Roaming not allowed by server
debug1: SSH2_MSG_SERVICE_REQUEST sent
debug1: SSH2_MSG_SERVICE_ACCEPT received
debug1: Authentications that can continue: publickey,gssapi-keyex,gssapi- with-mic,password
debug1: Next authentication method: gssapi-keyex
debug1: No valid Key exchange context
debug1: Next authentication method: gssapi-with-mic
debug1: Unspecified GSS failure. Minor code may provide more information
Credentials cache file '/tmp/krb5cc_0' not found
debug1: Unspecified GSS failure. Minor code may provide more information
Credentials cache file '/tmp/krb5cc_0' not found
debug1: Unspecified GSS failure. Minor code may provide more information
debug1: Unspecified GSS failure. Minor code may provide more information
debug1: Next authentication method: publickey
debug1: Trying private key: /root/.ssh/id_rsa
debug1: Trying private key: /root/.ssh/id_dsa
debug1: Next authentication method: password
Wani@localhost's password:
debug1: Authentication succeeded (password).
Authenticated to localhost ([127.0.0.1]:22).
debug1: channel 0: new [client-session]
debug1: Requesting no-more-sessions@openssh.com
debug1: Entering interactive session.
debug1: Sending environment.
debug1: Sending env XMODIFIERS = @im=none
debug1: Sending env LANG = en_US.UTF-8
debug1: Sending command: scp -v -t -- .
Hello
[root@Dell Wani]# 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
Transferred: sent 1664, received 1976 bytes, in 0.1 seconds
Bytes per second: sent 22961.5, received 27266.8
debug1: Exit status 0
(后我preSS输入)
(And After I press Enter)
[root@Dell Wani]#
任何人都可以请一些线索,以什么这里究竟发生了什么?为什么文件没有得到根本复制到迩?
Can anyone please shed some light as to what exactly happened here? Why did the file not get copied to Wani from root?
推荐答案
使用回声
在的.bashrc
将突破 SCP
,因为 SCP
希望看到在标准输入/输出通道的协议数据。见<一href=\"https://bugzilla.redhat.com/show_bug.cgi?id=20527\">https://bugzilla.redhat.com/show_bug.cgi?id=20527就这一问题进行更多的讨论。
Using echo
in a .bashrc
will break scp
, as scp
expects to see its protocol data over the stdin/stdout channels. See https://bugzilla.redhat.com/show_bug.cgi?id=20527 for more discussion on this issue.
有几个解决方法可供选择:
There's a few workarounds available:
- 在互动标志的条件(例如
案例$ - 在* I *
由tripleee建议) - 使用
的tty
程序检测一个交互式shell(如如果TTY&GT;的/ dev / null的
或如果[-t 0]
) - 检查值
$ SSH_TTY
- Condition on the 'interactive' flag (e.g.
case $- in *i*
as suggested by tripleee) - Use the
tty
utility to detect an interactive shell (e.g.if tty > /dev/null
orif [ -t 0 ]
) - Check the value of
$SSH_TTY
我想你应该使用哪一个对你有用。我不知道最好的(最便携/最可靠)的选择是什么,很遗憾。
I suppose you should use whichever one works for you. I don't know what the best (most portable/most reliable) option is, unfortunately.
这篇关于在.bashrc中回响时,SCP不起作用?的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持!