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
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
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)
