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 Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1900429 Title: [snap] Unable to access files owned by another user Status in chromium-browser package in Ubuntu: Invalid Bug description: The chromium snap cannot access files in my $HOME that have a different owner, even though the files are world-readable. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1900429/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
