Deprecation of scp protocol and improving sftp client
jjelen at redhat.com
Wed Jun 17 02:41:09 AEST 2020
I believe we all can agree that scp is ugly protocol carried for ages
only for its simplicity of its usage and really no dependencies as it
is installed together with every ssh client. But as we have seen
recently, its simplicity and flexibility comes with security issues
, it does not have great performance and there is really no
development in there.
Over the years, we still keep recommending people to use sftp instead,
but its api is not that flexible and simple to be usable as a drop-in
replacement in scripts nor for the occasional ad-hoc transfers of few
files from one server to another.
Before I start hacking, I would like to hear some opinions from others,
whether this is something planned, welcomed or whether there are some
good reasons to keep scp alive.
I have in my mind three things/steps that would make it possible:
* Update sftp client to be drop-in replacement for scp
* Change scp to use sftp internally
* Modify sshd to use some compatibility "scpd" to support old clients
and some time later
* Remove scp or replace it with a symlink
Senior Software Engineer
Red Hat, Inc.
More information about the openssh-unix-dev