Deprecation of scp protocol and improving sftp client

[Blumenthal, Uri - 0553 - MITLL]

On 8/3/20, 14:40, "openssh-unix-dev on behalf of Christoph Anton Mitterer" <openssh-unix-dev-bounces+uri=ll.mit.edu at mindrot.org on behalf of calestyo at scientia.net> wrote:
    >> That would be the same as killing scp…
    >
    > Better that... than having an inherently insecure scp...

Not for me! Security provided by "scp" satisfies *my* use case.

    > or at least
    > make it absolutely clear and rename it to i[nsecure]scp.

Couldn't care less. There's a saying "You may call me 'pot' - just don't stick me into the oven"

    > If the core functionality of a program (which is here probably the
    > "secure") is no longer given, then it's IMO better to rather cause
    > breakage (at least for old clients), than to keep going.

Again. For me that remote path expansion is not the "core". The "core" is the ability to do "cp" from one host within my security domain to another. 

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 5249 bytes
Desc: not available
URL: <http://lists.mindrot.org/pipermail/openssh-unix-dev/attachments/20200803/51f7fe87/attachment-0001.p7s>