I am having a similar problem (though with ssh, rather than scp).
I have long had a setup where I run tunnels over ssh (in both
directions) between munnari.oz.au and me at home. The latter
(me@home) has a new 9.99.97 system in the process of being installed.
I have a pseudo-host "work" (not a
On Sat, Jun 11, 2022 at 08:48:10AM -0700, Brian Buhrow wrote:
> Hello. What version of openssh are you using? I just tested between
> NetBSD-5.2 and
> -current as of 99.77. Those versions are:
> 5.2: OpenSSH_5.0 NetBSD_Secure_Shell-20080403-hpn13v1
> 99.77: OpenSSH_8.4
Hello. What version of openssh are you using? I just tested between
NetBSD-5.2 and
-current as of 99.77. Those versions are:
5.2: OpenSSH_5.0 NetBSD_Secure_Shell-20080403-hpn13v1
99.77: OpenSSH_8.4 NetBSD_Secure_Shell-20201204-hpn13v14-lpk,
your command, with a nested directory, works
On Sat, Jun 11, 2022 at 10:56:26AM -0400, Tom Lane wrote:
> Experimenting here, it seems the only case that doesn't work is
> scp -r *to* a remote directory that doesn't exist yet. Possibly
> worthy of a PR.
Yes, it is an upstream regression when they switched the default protocol.
A NetBSD PR
Thomas Klausner writes:
> I cannot use 'scp -r' from -current to NetBSD 8 or NetBSD 9.
That surprised me, because I've been using it regularly, but
mostly to copy files from a 9.2 machine to -current.
Experimenting here, it seems the only case that doesn't work is
scp -r *to* a remote directory
On Sat, Jun 11, 2022 at 04:12:17PM +0200, Thomas Klausner wrote:
> Hi!
>
> I cannot use 'scp -r' from -current to NetBSD 8 or NetBSD 9.
scp changed to use sftp by default in a recent OpenSSH update. It seems
you can use scp -O to request the legacy protocol.
Martin
Hi!
I cannot use 'scp -r' from -current to NetBSD 8 or NetBSD 9.
> scp -r a target:
scp: realpath ./a: No such file
scp: upload "./a": path canonicalization failed
scp: failed to upload directory a to .
scp without -r still works fine.
Is there a compatibility setting I can enable to make this
