I don’t think the majority of users even know what’s under the hood of scp, let alone care. So, whatever change one can make that is transparent to the users *and* doesn’t negatively impact performance, is bound to be a winner. Somehow, I doubt sftp can provide that, but I’d be happy to be proven wrong here. Regards, Uri > On Jun 16, 2020, at 14:02, Stuart Henderson <stu@xxxxxxxxxxxxxxx> wrote: > > On 2020/06/16 17:37, Peter Stuge wrote: >> Jakub Jelen wrote: >>> Any ideas/comments/suggestions? >> >> I doubt that upstream would drop the scp utility and protocol easily. >> There is no point in breaking compatibility > > OpenSSH does break compatibility where there's good reason to. > SSH 1, <1024 bit keys. > > _______________________________________________ > openssh-unix-dev mailing list > openssh-unix-dev@xxxxxxxxxxx > https://lists.mindrot.org/mailman/listinfo/openssh-unix-dev
Attachment:
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ openssh-unix-dev mailing list openssh-unix-dev@xxxxxxxxxxx https://lists.mindrot.org/mailman/listinfo/openssh-unix-dev
