On 2018-08-28 11:39:08 -0700, Chris Waters wrote: > Programs are allowed to use the environment to communicate with each > other. Programs *do*. If you assume they won't, you're likely to > experience more "breakage". The problem is not with these programs; > the problem is with your assumptions.
But that would have been possible without breaking everything (e.g. by checking the owner of the directory before writing anything there). And this is not my assumptions, but assumptions implied by historical su's behavior. > > I've reported a bug against su: > > The behavior of su is defined by POSIX and the Single User Spec. It's > not a bug. No, su is not part of the utilities described by POSIX. And if it were, that would have been a very strong argument against the dconf behavior. > > And you're suggesting sudo while there will be the same issue. > > No. The sudo -e option doesn't run your editor as root; Unfortunately, this is not documented and the sentence "Note that unlike most commands run by sudo, the editor is run with the invoking user's environment unmodified." is confusing. Instead of saying "with the invoking user's environment unmodified", it should have said "without becoming the other user". -- Vincent Lefèvre <vinc...@vinc17.net> - Web: <https://www.vinc17.net/> 100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/> Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)
