On 11/2/20 4:05 PM, Marius Schwarz wrote:
Am 02.11.20 um 15:44 schrieb Jakub Jelen:
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.
if it is compatible with what powerusers i.e. sysadmins do with it, it
should be fine. I have such things as Compression, Cipher, Ports and 2
sets of login credentials in mind, to directly copy from a to b without
parking it first on the pc running the scp.
Compression, Ciphers and Ports are configuration options for ssh
protocol, which stays unchanged.
Copying remote to remote (without the -3 option) should work after
updating scp also on the remote source machine.
On the server side it has to honor things like CHROOT directives.
This is also a property/configuration of ssh server. Using chroot with
sftp is much easier than with scp as you really do not need any binaries
in chroot and you can use internal-sftp server.
Regards,
--
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
