Re: SELinux status report and call to action

2021-01-13 Thread Dominick Grift
e allowed to function. I addressed most of the basic LuCI apects. So the basics work but again there are many optional modules that have to be supported and then tested. > > David Lang > >  On Wed, 13 Jan 2021, Dac Override wrote: > >> Date: Wed, 13 Jan 2021 17:34:56 +0100 >&g

Re: Re: SELinux status report and call to action

2021-01-13 Thread David Lang
ct: Re: Re: SELinux status report and call to action Hello Alberto, Thanks for you input. I agree that leveraging SELinux is, like for example leveraging Linux netfilter, not trivial. SELinux is however well documenting and with the exception of OpenWrt specifics it might not be productive to yet agai

Re: Re: SELinux status report and call to action

2021-01-13 Thread Dac Override
Hello Alberto, Thanks for you input. I agree that leveraging SELinux is, like for example leveraging Linux netfilter, not trivial. SELinux is however well documenting and with the exception of OpenWrt specifics it might not be productive to yet again document aspects that are already published

Re: SELinux status report and call to action

2021-01-13 Thread Alberto Bursi
On 12/01/21 18:27, Dominick Grift wrote: - My question to the reader is: why haven't you enabled SELinux yet on your test builds at least? Or maybe you have but you havent given any feedback. Why is that? Thanks, Lack of documentation. Selinux is not an easy topic

Re: SELinux status report and call to action

2021-01-13 Thread Dominick Grift
On 1/12/21 6:27 PM, Dominick Grift wrote: > > Community, > > Optional SELinux support has been added to OpenWrt for a while now and I > gave a talk about the status at "Battle of the meshes 13th edition". > > There was a comment mentioning that there was an impression that > "rolling out