Bug#198275: /usr/bin/scp: scp: no way to escape colons in pathnames
Package: ssh
Version: 1:3.8.1p1-8.sarge.4
Followup-For: Bug #198275
I was just trying to copy a folder over with a colon in it's name. Of
course, scp thought that the colon was a hostname separator and responded
with "ssh: The: Name or service not known"
So, I tried backslashing the colon, and replacing it with two colons. Both
had the exact same result.
I tried prefixing the entire pathname with a colon. That caused it to at
least stop thinking of it as a separator; the problem there was that it also
included the prefix in the path...
":The ...: No such file or directory"
I think that the best way to solve this (short of telling people not to try
to copy files with colons in their name <g>), is to make it so that if a
pathname begins with a colon, that colon is removed and the path is
considered to be part of the local filesystem.
Cheers,
Tyler
-- System Information:
Debian Release: 3.1
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.8-2-686
Locale: LANG=en_CA, LC_CTYPE=en_CA (charmap=ISO-8859-1)
Versions of packages ssh depends on:
ii adduser 3.63 Add and remove users and groups
ii debconf 1.4.47 Debian configuration management sy
ii dpkg 1.10.27 Package maintenance system for Deb
ii libc6 2.3.2.ds1-20 GNU C Library: Shared libraries an
ii libpam-modules 0.76-22 Pluggable Authentication Modules f
ii libpam-runtime 0.76-22 Runtime support for the PAM librar
ii libpam0g 0.76-22 Pluggable Authentication Modules l
ii libssl0.9.7 0.9.7e-3 SSL shared libraries
ii libwrap0 7.6.dbs-8 Wietse Venema's TCP wrappers libra
ii zlib1g 1:1.2.2-4 compression library - runtime
-- debconf information:
ssh/insecure_rshd:
ssh/user_environment_tell:
* ssh/forward_warning:
ssh/insecure_telnetd:
ssh/new_config: true
* ssh/use_old_init_script: true
* ssh/SUID_client: true
* ssh/disable_cr_auth: false
ssh/ssh2_keys_merged:
* ssh/protocol2_only: true
ssh/encrypted_host_key_but_no_keygen:
* ssh/run_sshd: true
Reply to: