smbnetfs cannot access libsecret unless run in foreground

Bug #1950927 reported by Matthew R. Dorozenski
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
smbnetfs (Ubuntu)
New
Undecided
Unassigned

Bug Description

Ubuntu 21.10
smbnetfs/impish,now 0.6.3-1 amd64

I am using smbnetfs to mount smb network shares. Credentials are stored in libsecret using secret-tools. Server name myserver. Share name public is unprotected. Share name myshare is protected by password. If I run:

smbnetfs mnt

there are no errors, and I can browse to public shares.

cd mnt/myserver/public
ls

gives the expected result and lists contents.

However,

cd mnt/myserver/myshare
ls

gives:

ls: cannot open directory 'mnt/myserver/myshare': Permission denied

However, if I run with either the -d (debug) or -f (foreground) option, (-d implies -f), and then in another terminal, or by backgrounding the running process, I run the above commands, I am able to browse both public and password protected shares without issue.

I suspect this has something to do with the ability to access information stored in libsecret when run in the background, but I'm not certain.

Everything works as expected if I use a .auth file for the credential storage (which is obviously less secure, but I tested it to help diagnose the issue).

Also - a side note - the -o use_libsecret option listed in the manual and with --help both error:

fuse: unknown option `use_libsecret=true'

If the option is set in the .smb/smbnetfs.conf file, the same error is reported. However, run in the foreground, without this option, libsecret is used correctly.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.