Damien Miller <d...@mindrot.org> wrote: > On Fri, 6 Aug 2021, Christian Weisgerber wrote: > > > Damien Miller: > > > > > Just a head-up: snaps currently contain a set of changes[1] to > > > make scp(1) use the SFTP protocol by default. > > > > > Please report any incompatibilities or bugs that you encounter here > > > (tech@), to bugs@ or to openssh@. > > > > An obvious cosmetic difference is that relative paths are prefixed > > with the home directory of the remote source in the progress bar: > > > > $ scp lorvorc:foo /dev/null > > /home/naddy/foo 100% 4099 1.6MB/s 00:00 > > > > $ scp -O lorvorc:foo /dev/null > > foo 100% 4099 3.7MB/s 00:00 > > > > > > I don't know if we care. > > Yeah, I'm inclined to leave the full paths unless there's a good argument > for truncating them.
1) Are there circumstances where the remote homedir expansion is slightly secret? 2) With very long names, it truncates the end of the path. This is less useful information. Imagine a copy operation with multiple files being transferred, one of them is huge and surprisingly long, but you cannot identify which one because all the truncated long paths are the same. 3) (old) scp and rsync show the path only component only. So.... I think the path-component-only scheme is better, and this should change.
