All you guys are reporting a completely different bug. The original
report was specifically about the output under -v, not about the need to
escape filenames inconveniently for scp.
While scp's behaviour is inconvenient, it is rather unlikely to change
since scp's interface is necessarily frozen f
Matt, as was stated 2 posts above, its the correct behavior to have to
double quote or add 3 backslashes.
--
scp doesn't report correct filenames with spaces in verbose mode
https://bugs.launchpad.net/bugs/89945
You received this bug notification because you are a member of Ubuntu
Server Team, wh
I'm still experiencing this bug.
--
scp doesn't report correct filenames with spaces in verbose mode
https://bugs.launchpad.net/bugs/89945
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openssh in ubuntu.
--
Ubuntu-server-bugs mailing l
If you run scp with the '-v' (verbose) you can see what command is
actually run. It should be in the first line of output.
Without using any \ or " (or ') the filename are treated by the local
shell as 3 arguments to scp instead of one; the filename.
In the first case the \ are expanded by the lo
could you care explain why is it this way?
--
scp doesn't report correct filenames with spaces in verbose mode
https://bugs.launchpad.net/bugs/89945
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openssh in ubuntu.
--
Ubuntu-server-bugs
or use quotes and single \ around the filename, i.e:
scp testmachine:"File\ with\ spaces" ./
--
scp doesn't report correct filenames with spaces in verbose mode
https://bugs.launchpad.net/bugs/89945
You received this bug notification because you are a member of Ubuntu
Server Team, which is subsc
Use tripple \ for escaping the space. I.e
scp testmachine:File\\\ with\\\ spaces ./
--
scp doesn't report correct filenames with spaces in verbose mode
https://bugs.launchpad.net/bugs/89945
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
Ubuntu 8.04, i386.
I can confirm that I can repeat the issue as demonstrated by eldragon. Problem
is not fixed. I cannot copy (scp) file with space in filename from one machine
to other.
--
scp doesn't report correct filenames with spaces in verbose mode
https://bugs.launchpad.net/bugs/89945
Yo
ok, this is not fixed at all, this is what i get when trying to scp a file
with an escaped character
[code]
[EMAIL PROTECTED]:~$ touch test\ file
[EMAIL PROTECTED]:~$ logout
Connection to emmet closed.
[EMAIL PROTECTED]:~$ scp [EMAIL PROTECTED]:test\ file ./
scp: test: No such file or directory
s
ok, this is not fixed at all, this is what i get when trying to scp a file
with an escaped character
[code]
[EMAIL PROTECTED]:~$ touch test\ file
[EMAIL PROTECTED]:~$ logout
Connection to emmet closed.
[EMAIL PROTECTED]:~$ scp [EMAIL PROTECTED]:test\ file ./
scp: test: No such file or directory
s
This bug was fixed in the package openssh - 1:4.7p1-8ubuntu1
---
openssh (1:4.7p1-8ubuntu1) hardy; urgency=low
* Resynchronise with Debian. Remaining changes:
- Add support for registering ConsoleKit sessions on login.
openssh (1:4.7p1-8) unstable; urgency=high
* Fill in CVE
Hmm, strnvis isn't quite right. I guess this unreliable quoting
(consider what happens if the filename contains a single quote!) is OK
for something that is just for human consumption, though I'd still like
something that actually corresponds to real shell quoting in future.
I'll apply a variant of
Should use strnvis instead, I suspect.
--
scp doesn't report correct filenames with spaces in verbose mode
https://bugs.launchpad.net/bugs/89945
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openssh in ubuntu.
--
Ubuntu-server-bugs mai
13 matches
Mail list logo
