[Bug 1900429] Re: [snap] Unable to access files owned by another user
That's a question that would be better answered by the snapd design/security team. May I suggest you ask it on https://forum.snapcraft.io/ (preferably keeping offending words out, this will help in getting answers and sparking a constructive conversation)? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1900429 Title: [snap] Unable to access files owned by another user To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1900429/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1900429] Re: [snap] Unable to access files owned by another user
In my case, a docker-based firmware build process produces a update package (owned by root, for some reason), which I upload to a target via a web-interface. Sure, I can change the owner of the files but still, this used to work and it doesn't now. Let me turn the question around. What is the use-case for prohibiting access to files in the user's home directory, which are readable by the user based on good old Unix filesystem permissions? Devising a completely parallel access policy based on arbitrary and invisible rules seems utterly stupid to me. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1900429 Title: [snap] Unable to access files owned by another user To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1900429/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1900429] Re: [snap] Unable to access files owned by another user
That's the intended behaviour, snapd's sandbox doesn't allow strictly confined snaps (such as chromium) to access files owned by someone else. Out of curiosity, what's the use case for files owned by a different owner in your home directory? ** Changed in: chromium-browser (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1900429 Title: [snap] Unable to access files owned by another user To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1900429/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
