Comment by philote
4 years ago
Can't you usually just put quotes around the filename and/or path to prevent all those issues?
Edit: nope, just tried it and scp still sees the quoted filename as a host + path
4 years ago
Can't you usually just put quotes around the filename and/or path to prevent all those issues?
Edit: nope, just tried it and scp still sees the quoted filename as a host + path
That is just lazy programming. If the input "foo:bar" is ambiguous, the program should try both interpretations (HOST:FILE and FILE) and then present the user with a prompt that provides sufficient information.
"Does foo:bar refer to the local file `foo:bar' (size: 102kB, date: 2021-11-11) or to the file `bar' on host `foo' (FQDN: foo.example.com, IP address: 1.2.3.4)?
1: local file `foo:bar'
2: file `bar' on remote host `foo'
Your selection: "