Re: [nicolas.io...@m4x.org: Re: Bash 5 change in behavior and SELinux]

2019-02-25 Thread Chet Ramey
On 2/24/19 3:50 PM, Dominick Grift wrote: > I noticed that Bash5 requires some additional permissions that I found > questionable. > > Mostly the listing of / and /home > > I am wondering whether there is a way to avoid the requirement for above > permissions. There is, at least in the most fr

Re: [nicolas.io...@m4x.org: Re: Bash 5 change in behavior and SELinux]

2019-02-24 Thread Grisha Levit
On Sun, Feb 24, 2019 at 5:14 PM Dominick Grift wrote: > > Simple test: This seems to be the same as https://lists.gnu.org/archive/html/bug-bash/2019-01/msg00276.html https://lists.gnu.org/archive/html/bug-bash/2019-02/msg0.html Which has been fixed in the devel branch

Re: [nicolas.io...@m4x.org: Re: Bash 5 change in behavior and SELinux]

2019-02-24 Thread Dominick Grift
Simple test: 21:54 So, the simple testcase, without SELinux : | 21:54 - sudo chmod a-r /home | 21:54 - cd $HOME | 21:54 - touch a.test | 21:54 - rm ~/*.test

[nicolas.io...@m4x.org: Re: Bash 5 change in behavior and SELinux]

2019-02-24 Thread Dominick Grift
I noticed that Bash5 requires some additional permissions that I found questionable. Mostly the listing of / and /home I am wondering whether there is a way to avoid the requirement for above permissions. After some digging with the help of the community we came up with the following analysis