IETF-SSH archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
Re: I-D ACTION:draft-ietf-secsh-scp-sftp-ssh-uri-00.txt
> I wrote:
>> - SCP is a bit harder, because AIUI there's no requirement for
>> absolute path names on an SCP server to begin with a slash, so
>> the stated syntax is potentially ambiguous. (A Windows SCP
>> server, for example, is at liberty to begin all its absolute path
>> names with "c:\" and "d:\" and so on, I believe.)
"Joseph Salowey" <jsalowey%cisco.com@localhost> wrote:
> I'm not sure, but I believe it is acceptable for the absolute path
> section to contain C: or d:.
>
> Scp://c:/file.txt
>
> Do you see an issue with this?
Well, the URI definition said
scp_URI = "scp://" [ userinfo "@" ] host [ ":" port ]
[ ; parameter = value ] [ abs_path ]
So the `abs_path' section starts immediately after the host name,
and hence it is expected to begin with a slash:
scp://hostname/usr/bin/thingy
^^^^^^^^^^^^^^^
If the abs_path doesn't begin with a slash, you get
scp://hostnamec:\bin\thingy
which is clearly useless (and that's without even going into the
backslash issue).
--
Simon Tatham "_shin_, n. An ingenious device for
<anakin%pobox.com@localhost> finding tables and chairs in the dark."
Home |
Main Index |
Thread Index |
Old Index