Python 使用Popen执行scp，无需输入密码
我有以下脚本 test.pyPython 使用Popen执行scp，无需输入密码,python,passwords,pipe,popen,scp,Python,Passwords,Pipe,Popen,Scp,我有以下脚本 test.py #!/usr/bin/env python2 from subprocess import Popen, PIPE, STDOUT proc = Popen(['scp', 'test_file', 'user@192.168.120.172:/home/user/data'], stdout=PIPE, stdin=PIPE, stderr=STDOUT) out, err = proc.communicate(input='userpass\n') prin
#!/usr/bin/env python2
from subprocess import Popen, PIPE, STDOUT
proc = Popen(['scp', 'test_file', 'user@192.168.120.172:/home/user/data'], stdout=PIPE, stdin=PIPE, stderr=STDOUT)
out, err = proc.communicate(input='userpass\n')
print('stdout: ' + out)
print('stderr: ' + str(err))
用户10.0.0.2/home/user/datatest\u文件userpasscommunicate（）proc.stdin.write('userpass\n')
proc.stdin.flush()
out, err = proc.communicate()
但是没有任何变化，我仍然收到了密码提示。当
scpsshstdin/dev/ttysshpasssshscpsshpasssshpasssshpass/*
Comment no. 3.14159
This comment documents the history of code.
We need to open the slavept inside the child process, after "setsid", so that it becomes the controlling
TTY for the process. We do not, otherwise, need the file descriptor open. The original approach was to
close the fd immediately after, as it is no longer needed.
It turns out that (at least) the Linux kernel considers a master ptty fd that has no open slave fds
to be unused, and causes "select" to return with "error on fd". The subsequent read would fail, causing us
to go into an infinite loop. This is a bug in the kernel, as the fact that a master ptty fd has no slaves
is not a permenant problem. As long as processes exist that have the slave end as their controlling TTYs,
new slave fds can be created by opening /dev/tty, which is exactly what ssh is, in fact, doing.
Our attempt at solving this problem, then, was to have the child process not close its end of the slave
ptty fd. We do, essentially, leak this fd, but this was a small price to pay. This worked great up until
openssh version 5.6.
Openssh version 5.6 looks at all of its open file descriptors, and closes any that it does not know what
they are for. While entirely within its prerogative, this breaks our fix, causing sshpass to either
hang, or do the infinite loop again.
Our solution is to keep the slave end open in both parent AND child, at least until the handshake is
complete, at which point we no longer need to monitor the TTY anyways.
*/
scp我不知道您是否可以从Python中实现这一点，但好消息是，标准库确实包含用于处理伪终端的函数：您可以改用公钥身份验证吗？那你就不必担心密码了。不，正如我提到的，scp是唯一的方法。我也为此感到不安，但事实就是这样D我知道我可以使用
expectpexepectsshpassscpscpscpssh/dev/ttytty