SMB support: must tell client or server what/how to mount stuff

[Antoine Martin]

Windows clients can't mount a remote tunneled server since we can't tell them what port to use (sigh). So maybe we should always do a reverse mount? (server mounts shares from the client)
We need to find out the list of shares (pysamba?) and allow the user to configure what is mounted (read-only, password,...)

The actual mounting is the easy part:

mount.cifs //127.0.0.1/public ./guest -o port=21062 -o guest

But we have to make sure we always unmount stuff when the server goes down... Problem is that some files might still be open!

We should also deal with non-tunneled setups nicely: simply connect to SMB on client or server directly. This weighs in favour of supporting client-mounts-server option.

We can figure out what shares are available with (needs a bit of magic parsing... sigh):

smbclient -U guest -N -L localhost

or

smbclient -A /path/to/auth-file -L localhost

​pysamba does not seem to help here, unless I am missing something.

See bug #91 for the next step.

[Antoine Martin]

Also check the mime mapping on Linux

[Antoine Martin]

part 1 in r1972: parse smbclient

[Antoine Martin]

large part done in r1975

[Antoine Martin]

now support non-tunneled mounts in r1979