3 ms·
Honestly this seems a bit disappointing to me. Reading the issue description scp sounds like the following pseudo-code: sock = connect(server) sock.do_
by blattimwind 8y ago
Honestly this seems a bit disappointing to me. Reading the issue description scp sounds like the following pseudo-code:
sock = connect(server)
sock.do_crypto()
sock.send_filelist(commandline.list)
cd(commandline.targetdir)
while not sock.eof:
write_to_local_disk(sock.receive_file())
i.e. blindly create and change files the server tells the client about. Complete lack of client-side verification.
- jolmg 8y ago> sock.send_filelist(commandline.list) Instead of a "filelist", it's got to be a remote shell command argument, since it allows stuff like: scp server:'$( comm -23 \ <(find dir1 -type f -printf "%P\n" | sort) \ <(find dir2 -type f -printf "%P\n" | sort) \ | sed "s:^:dir1/:" )' . I'm not sure what you propose for client-side verification in this case.