On Mon, May 14, 2018 at 4:19 PM, Jason Zaman wrote:
> On Mon, May 14, 2018 at 09:30:41AM -0400, Stephen Smalley wrote:
>> On 05/13/2018 07:43 AM, Nicolas Iooss wrote:
>> > On Sat, May 12, 2018 at 2:53 PM, Matěj Cepl wrote:
>> >> Hi,
>> >>
>> >> I am changing jobs (Red Hat -> SUSE; R&D, but not a
On Mon, May 14, 2018 at 09:30:41AM -0400, Stephen Smalley wrote:
> On 05/13/2018 07:43 AM, Nicolas Iooss wrote:
> > On Sat, May 12, 2018 at 2:53 PM, Matěj Cepl wrote:
> >> Hi,
> >>
> >> I am changing jobs (Red Hat -> SUSE; R&D, but not a security
> >> related job), and although I will be switching
On 05/13/2018 07:43 AM, Nicolas Iooss wrote:
> On Sat, May 12, 2018 at 2:53 PM, Matěj Cepl wrote:
>> Hi,
>>
>> I am changing jobs (Red Hat -> SUSE; R&D, but not a security
>> related job), and although I will be switching my workstation to
>> OpenSUSE, I would love to keep SELinux working. Which m
On Sat, May 12, 2018 at 8:53 AM Matěj Cepl wrote:
> Hi,
> I am changing jobs (Red Hat -> SUSE; R&D, but not a security
> related job), and although I will be switching my workstation to
> OpenSUSE, I would love to keep SELinux working. Which meant I had
> to dig into the current situation of SEL
On Sat, May 12, 2018 at 2:53 PM, Matěj Cepl wrote:
> Hi,
>
> I am changing jobs (Red Hat -> SUSE; R&D, but not a security
> related job), and although I will be switching my workstation to
> OpenSUSE, I would love to keep SELinux working. Which meant I had
> to dig into the current situation of SE
Hi,
I am changing jobs (Red Hat -> SUSE; R&D, but not a security
related job), and although I will be switching my workstation to
OpenSUSE, I would love to keep SELinux working. Which meant I had
to dig into the current situation of SELinux and it is … not
good. So, I started to repackage all SELi
