Given a samba share on debian server which allows READ ONLY access to anonymous and READ WRITE access to my named user: kpeter.
There is no way to write on this share because gvfs always connects as anonymous, there is no way to specify my user/pass.
If I mount manually with explicit username things became stanger:
Let say:
$ gvfs-mount smb://kpeter@duron/projects/
It works, I can see the mounted share on my desktop.
$ gvfs-mount -l
Mount(0): projects ezen: duron -> smb://duron/projects/
After opening the share with nautilus a second mount appears on the desktop:
$ gvfs-mount -l
Mount(0): projects ezen: duron -> smb://duron/projects/
Mount(1): projects ezen: duron -> smb://duron/projects/
I think that this second mount is anonymous and it is very bad...
I have a very similar problem:
Given a samba share on debian server which allows READ ONLY access to anonymous and READ WRITE access to my named user: kpeter.
There is no way to write on this share because gvfs always connects as anonymous, there is no way to specify my user/pass.
If I mount manually with explicit username things became stanger:
Let say: duron/projects/
$ gvfs-mount smb://kpeter@
It works, I can see the mounted share on my desktop. projects/
$ gvfs-mount -l
Mount(0): projects ezen: duron -> smb://duron/
After opening the share with nautilus a second mount appears on the desktop: projects/ projects/
$ gvfs-mount -l
Mount(0): projects ezen: duron -> smb://duron/
Mount(1): projects ezen: duron -> smb://duron/
I think that this second mount is anonymous and it is very bad...