New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Can -oallow_other be passed to fuse when mounting? #26
Comments
rfjakob
added a commit
that referenced
this issue
May 16, 2016
As requested in #26 , this adds the option to allow other users to access the filesystem.
rfjakob
added a commit
that referenced
this issue
May 16, 2016
As requested in #26 , this adds the option to allow other users to access the filesystem.
No, not yet, but I have started working on it. It's a simple addition but I have hit an issue in the fuse library ( hanwen/go-fuse#107 ). Should be resolved shorty, stay tuned. |
rfjakob
added a commit
that referenced
this issue
May 18, 2016
As requested in #26 , this adds the option to allow other users to access the filesystem.
Fixed in e7f7813 . Please report back if you hit any problems. |
Hi, |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Sorry, don't know if this is an issue, or just my not knowing how to do something. I want to samba share my unencrypted fuse mount and my understanding is that fuse needs -oallow_other sent to it upon mount request. Is there a way to get gocryptfs to pass this flag through to fuse when starting/mounting my encrypted directory?
(You may think I'm mad to samba share this, but it's for very transient use between a group of people in an enclosed private network)
The text was updated successfully, but these errors were encountered: