On 11/2/20 3:57 PM, Walter Cazzola wrote:
Hi,
I don't know if and how the internet protocol scp: is related to the scp
command. But I suppose it is.
Hi,
SCP is not an internet protocol -- it is simple protocol that is used
inside of encrypted SSH session, similarly to SFTP protocol. The name
comes from RCP which actually was unencrypted internet protocol and
which is hopefully gone.
I'm using scp: a lot to edit remote files with vim and I'm pretty sure that
many remote admins are doing the same.
So I'm wondering how this change will affect my use case scenario and if
you
have considered it when moving to sftp.
That is a good question!
When I try to use scp://host/file I am getting errors that vim is trying
to use `rcp` command (yuck!). But using the same with sftp://host/file
works like a charm.
I believe vim is using just scp to fetch the file so if the connection
to the server will work also with sftp, it should continue to work (but
I recommend using sftp protocol anyway).
The simplest way to try is to try with sftp:// or try the previously
mentioned package, but my best bet is that it will keep on working as
before (even though I never used this inside of vim up until today).
Regards,
Jakub
Thank you
Walter
On Mon, 2 Nov 2020, Jakub Jelen wrote:
Hi Fedora users!
Over the last years, there were several issues in the SCP protocol,
which lead us into discussions if we can get rid of it in upstream
[1]. Most of the voices there said that they use SCP mostly for simple
ad-hoc copy and because sftp utility does not provide simple interface
to copy one or couple of files back and forth and because of people
are just used to write scp rather than sftp.
Some months ago, I wrote a patch [2] for scp to use SFTP internally
(with possibility to change it back using -M scp) and ran it through
some successful testing. The general feedback from upstream was also
quite positive so I would like to hear also opinions from our users.
It still has some limitations (missing -3 support, it will not work if
the server does not run sftp subsystem, ...), but it should be good
enough for most common use cases.
Today, I set up a copr repository with the current openssh from Fedora
+ the patch [2] for anyone to test and provide feedback, either here
on the mailing list, or in the github PR according to ones preferences.
I am looking for any kind of feedback from the idea through the
usability, implementation. Is this something you would like to see in
Fedora soon? Do you have something against this? Is your use case
missing?
[1]
https://lists.mindrot.org/pipermail/openssh-unix-dev/2020-June/038594.html
[2] https://github.com/openssh/openssh-portable/pull/194/
[3] https://copr.fedorainfracloud.org/coprs/jjelen/openssh-sftp/
Thanks,
--
Jakub Jelen
Senior Software Engineer
Crypto Team, Security Engineering
Red Hat, Inc.
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
