[Bug 425] Network UNC path handling

http://bugs.winehq.org/show_bug.cgi?id=425

--- Comment #37 from François Gouget  2013-03-05 05:43:29 CST ---
As far as I can tell nothing has changed since the bug has been opened and the
issue is still present. For instance my computer runs Samba and exports
'\amboise\fgouget' yet:
 * Wine does not automatically create a drive for that share.
 * Wine (including winecfg.exe) does not show any awareness of that share.
 * Trying to open '\amboise\fgouget\foo.txt' in notepad fails complaining the
file does not exist (i.e. it's not asking for a password or complaining about
access rights).
 * Creating an 'fgouget' symbolic link to $HOME in
'~/.wine/dosdevices/unc/amboise' does not help. So the workaround mentioned in
comment #2 and others does not seem to even work anymore.

Comments 22 to 31 are unrelated to this bug. But if I were to open a new bug
today I think I would simply copy/paste comment #0 with two changes:
> - allow for a way to prevent applications to do all the above operations
> for obvious security reasons

It's up to the SMB/CIFS server to ensure that only authorized users have access
to the files it hosts, not Wine. Also a Windows application should be able to
do everything a native application can do. Any application-specific
restrictions should be provided by a sandboxing mechanism that's independent
from Wine.
> - provide a (Winelib) applet to let users mount/unmount drives while Wine
> is running

I'd mention that this applet could either be winecfg.exe or explorer.exe (which
is where it's done on Windows).