Re: [fuse-devel] syntax problem with fuse and sourceforge

[Miklos S. <mi...@sz...>]

On Tue, 7 Oct 2008, Graham Toal wrote:
> (I tried to post this to fuse-sshfs a few weeks ago but it bounced)
> 
> 
> Sourceforge uses a rather strange syntax to pass the unix group in to sftp
> along with the username, so in order to mount my sourceforge web area
> with sshfs I need to issue a command that looks something like this:
> 
>   sshfs gtoal,ec...@fr...:/ ~/sourceforge -o
> nonempty,reconnect,allow_root
> 
> This causes the error that "ec...@fr... is not a valid option"...
> 
> I've tried escaping the user,group string with " or ' but that didn't
> make any difference.
> 
> Inserting a \ before the comma does pass the comma through but
> unfortunately it also passes the \ through, so that's no use either.
> 
> Is this a user error (and if so what's the workaround) or is it a genuine
> problem with fuse and/or sshfs?

It is in both.  I've now added a fix (or rather a workaround) to the
CVS version of sshfs.

>  It shouldn't try to parse an object
> that doesn't
> start with '-' ..?

It doesn't do that.  The problem is that sshfs adds a new like this to
the command line:

  fsname=user@host:/path

Then if the username happens to contain a comma, it will think that
the fsname option is finished and a new option has started.

Currently there's no way to escape commas in fuse options, so the
workaround in sshfs is to simply remove all commas from fsname.

The proper fix is to add comma escaping to libfuse and use that in
sshfs.  I've added this to my todo list.

Thanks,
Miklos