sftp bugs

[Robert Collins]

On Thu, 2005-12-01 at 12:11 -0800, Robey Pointer wrote:

> Not necessarily.  I tried to explain this in an email yesterday but  
> probably just confused the issue. :)
> 
> Basically, all SFTP says is that the path can be absolute or  
> relative.  It doesn't say relative to what.  OpenSSH chooses to make  
> it relative to your home folder, because that's convenient, and it  
> knows you have a home folder.  A dedicated standalone SFTP server may  
> not be using unix shell accounts for authentication, so you may not  
> even have a home folder.  It might make paths relative to your  
> project folder, or an arbitrary folder that it thinks is convenient.
> 
> It may be hard to imagine right now, since almost all SFTP servers  
> are OpenSSH based, but I know of at least two all-python standalone  
> SFTP servers, so in the future we're probably going to see more SFTP  
> URLs where your authentication is not backed by a unix shell account  
> or home folder.

That makes sense to me. So the question is:

is sftp://host//absolute/path
or
is sftp://host/absolute/path

more useful?

For HTTP, FTP, and File:// urls the latter syntax is used: the
presumption is that all resources on the filesystem have the same
location *regardless* of user credentials.

I think that this is easier to debug and easier to understand than URL's
where the resource location randomly changes if the credentials change.

Rob

-- 
GPG key available at: <http://www.robertcollins.net/keys.txt>.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
Url : https://lists.ubuntu.com/archives/bazaar/attachments/20051202/34c28251/attachment.pgp