On Monday, November 2, 2020 4:47:47 PM CET Simo Sorce wrote: > On Mon, 2020-11-02 at 16:36 +0100, Kamil Dudka wrote: > > How is the "compatibility scpd to support old clients" going to differ > > from the current implementation? > > > > libcurl implements its own SCP client over libssh. Will this > > implementation > > continue to work after OpenSSH gets updated on servers? > > > > Applications often allow users to pass arbitrary URLs to libcurl. So one > > can, > > for example, use scp:// URLs to specify a kickstart for Anaconda. > > The fact that scp utility will be reimplemented over SFTP does not help > > much in this case. Each build of libcurl that supports scp:// supports > > sftp:// as well. But libcurl will not transmit scp:// requests over > > sftp:// in case SCP is not supported by the remote server any more. > > > Sounds like a RFE for libcurl to slowly move scp:// to be using the > sftp protocol instead ? As far as I know, (lib)curl has never silently transformed a protocol scheme explicitly specified with URL. This can be discussed upstream but I do not feel like starting the discussion myself. > Or they could simply deprecate it, and then users will have to change > their config to say sftp:// > > For something like libcurl the latter is probably more appropriate > anyway. Yes, I believe this is the curl way to handle it. Nothing is being changed for curl now as I understand it. So there is no need to take an immediate action. Anyway, I will notify curl upstream about the plan so they are not surprised later on. Kamil > Simo. > > -- > Simo Sorce > RHEL Crypto Team > 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
