Comment 2 for bug 1900429

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.