share encfs folder within the same group
given an encfs folder mounted under its own user, is it possible to permit read access to someone else (especially a system user), who belongs to the same group?
For example user1 owns encrypted_folder
user1:group1 - mounted:
$ drwxrwxrwx user1 group1 encrypted_folder
For user2 it looks like:
$ d????????? ? ? encrypted_folder
That leads to an "permission denied" error, if user2 wants to access that folder.
So is it possible to grand user2 access to that folder in order read some files from it? How does it looks like, if user2 is a system user?
linux permissions mount group fuse
edited Dec 14 '15 at 23:08
Gilles
534k12810771595
asked Dec 14 '15 at 12:24
eatdaseatdas
62
migrated from stackoverflow.com Dec 14 '15 at 16:33
This question came from our site for professional and enthusiast programmers.
add a comment |
given an encfs folder mounted under its own user, is it possible to permit read access to someone else (especially a system user), who belongs to the same group?
For example user1 owns encrypted_folder
user1:group1 - mounted:
$ drwxrwxrwx user1 group1 encrypted_folder
For user2 it looks like:
$ d????????? ? ? encrypted_folder
That leads to an "permission denied" error, if user2 wants to access that folder.
So is it possible to grand user2 access to that folder in order read some files from it? How does it looks like, if user2 is a system user?
linux permissions mount group fuse
edited Dec 14 '15 at 23:08
Gilles
534k12810771595
asked Dec 14 '15 at 12:24
eatdaseatdas
62
migrated from stackoverflow.com Dec 14 '15 at 16:33
This question came from our site for professional and enthusiast programmers.
add a comment |
given an encfs folder mounted under its own user, is it possible to permit read access to someone else (especially a system user), who belongs to the same group?
For example user1 owns encrypted_folder
user1:group1 - mounted:
$ drwxrwxrwx user1 group1 encrypted_folder
For user2 it looks like:
$ d????????? ? ? encrypted_folder
That leads to an "permission denied" error, if user2 wants to access that folder.
So is it possible to grand user2 access to that folder in order read some files from it? How does it looks like, if user2 is a system user?
linux permissions mount group fuse
edited Dec 14 '15 at 23:08
Gilles
534k12810771595
asked Dec 14 '15 at 12:24
eatdaseatdas
62
given an encfs folder mounted under its own user, is it possible to permit read access to someone else (especially a system user), who belongs to the same group?
For example user1 owns encrypted_folder
user1:group1 - mounted:
$ drwxrwxrwx user1 group1 encrypted_folder
For user2 it looks like:
$ d????????? ? ? encrypted_folder
That leads to an "permission denied" error, if user2 wants to access that folder.
So is it possible to grand user2 access to that folder in order read some files from it? How does it looks like, if user2 is a system user?
linux permissions mount group fuse
linux permissions mount group fuse
edited Dec 14 '15 at 23:08
Gilles
534k12810771595
asked Dec 14 '15 at 12:24
eatdaseatdas
62
edited Dec 14 '15 at 23:08
Gilles
534k12810771595
asked Dec 14 '15 at 12:24
eatdaseatdas
62
edited Dec 14 '15 at 23:08
Gilles
534k12810771595
edited Dec 14 '15 at 23:08
Gilles
534k12810771595
edited Dec 14 '15 at 23:08
Gilles
534k12810771595
534k12810771595
asked Dec 14 '15 at 12:24
eatdaseatdas
62
asked Dec 14 '15 at 12:24
eatdaseatdas
62
asked Dec 14 '15 at 12:24
eatdaseatdas
62
62
migrated from stackoverflow.com Dec 14 '15 at 16:33
This question came from our site for professional and enthusiast programmers.
migrated from stackoverflow.com Dec 14 '15 at 16:33
This question came from our site for professional and enthusiast programmers.
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
You're looking for this encfs flag?
--public
Attempt to make encfs behave as a typical multi-user filesystem. By default, all FUSE based filesystems are visible only to the user who mounted them. No other users (including root) can view the filesystem contents. The --public option does two things. It adds the FUSE flags "allow_other" and "default_permission" when mounting the filesystem, which tells FUSE to allow other users to access the filesystem, and to use the ownership permissions provided by the filesystem. Secondly, the --public flag changes how encfs's node creation functions work - as they will try and set ownership of new nodes based on the caller identification.
Warning: In order for this to work, encfs must be run as root -- otherwise it will not have the ability to change ownership of files. I recommend that you instead investigate if the fuse allow_other option can be used to do what you want before considering the use of --public.
Next time, RTFM :)
answered Dec 14 '15 at 16:52
Xen2050Xen2050
1,252813
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "106"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f249312%2fshare-encfs-folder-within-the-same-group%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
You're looking for this encfs flag?
--public
Attempt to make encfs behave as a typical multi-user filesystem. By default, all FUSE based filesystems are visible only to the user who mounted them. No other users (including root) can view the filesystem contents. The --public option does two things. It adds the FUSE flags "allow_other" and "default_permission" when mounting the filesystem, which tells FUSE to allow other users to access the filesystem, and to use the ownership permissions provided by the filesystem. Secondly, the --public flag changes how encfs's node creation functions work - as they will try and set ownership of new nodes based on the caller identification.
Warning: In order for this to work, encfs must be run as root -- otherwise it will not have the ability to change ownership of files. I recommend that you instead investigate if the fuse allow_other option can be used to do what you want before considering the use of --public.
Next time, RTFM :)
answered Dec 14 '15 at 16:52
Xen2050Xen2050
1,252813
add a comment |
You're looking for this encfs flag?
--public
Attempt to make encfs behave as a typical multi-user filesystem. By default, all FUSE based filesystems are visible only to the user who mounted them. No other users (including root) can view the filesystem contents. The --public option does two things. It adds the FUSE flags "allow_other" and "default_permission" when mounting the filesystem, which tells FUSE to allow other users to access the filesystem, and to use the ownership permissions provided by the filesystem. Secondly, the --public flag changes how encfs's node creation functions work - as they will try and set ownership of new nodes based on the caller identification.
Warning: In order for this to work, encfs must be run as root -- otherwise it will not have the ability to change ownership of files. I recommend that you instead investigate if the fuse allow_other option can be used to do what you want before considering the use of --public.
Next time, RTFM :)
answered Dec 14 '15 at 16:52
Xen2050Xen2050
1,252813
add a comment |
You're looking for this encfs flag?
--public
Attempt to make encfs behave as a typical multi-user filesystem. By default, all FUSE based filesystems are visible only to the user who mounted them. No other users (including root) can view the filesystem contents. The --public option does two things. It adds the FUSE flags "allow_other" and "default_permission" when mounting the filesystem, which tells FUSE to allow other users to access the filesystem, and to use the ownership permissions provided by the filesystem. Secondly, the --public flag changes how encfs's node creation functions work - as they will try and set ownership of new nodes based on the caller identification.
Warning: In order for this to work, encfs must be run as root -- otherwise it will not have the ability to change ownership of files. I recommend that you instead investigate if the fuse allow_other option can be used to do what you want before considering the use of --public.
Next time, RTFM :)
answered Dec 14 '15 at 16:52
Xen2050Xen2050
1,252813
You're looking for this encfs flag?
--public
Attempt to make encfs behave as a typical multi-user filesystem. By default, all FUSE based filesystems are visible only to the user who mounted them. No other users (including root) can view the filesystem contents. The --public option does two things. It adds the FUSE flags "allow_other" and "default_permission" when mounting the filesystem, which tells FUSE to allow other users to access the filesystem, and to use the ownership permissions provided by the filesystem. Secondly, the --public flag changes how encfs's node creation functions work - as they will try and set ownership of new nodes based on the caller identification.
Warning: In order for this to work, encfs must be run as root -- otherwise it will not have the ability to change ownership of files. I recommend that you instead investigate if the fuse allow_other option can be used to do what you want before considering the use of --public.
Next time, RTFM :)
answered Dec 14 '15 at 16:52
Xen2050Xen2050
1,252813
answered Dec 14 '15 at 16:52
Xen2050Xen2050
1,252813
answered Dec 14 '15 at 16:52
Xen2050Xen2050
1,252813
answered Dec 14 '15 at 16:52
Xen2050Xen2050
1,252813
1,252813
add a comment |
add a comment |
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f249312%2fshare-encfs-folder-within-the-same-group%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
