Bug#900580: Please restore SELinux context after creating the files in /var/lib/texmf

2018-06-04 Thread Laurent Bigonville
Le 04/06/18 à 02:09, Norbert Preining a écrit : Hi Laurent, 3) Copy the files instead of moving them, copied files ends with the label of their parent folder I think I will implement this change upstream, so that other distributions will profit from it at the same time. Yeah that's why I was

Bug#900580: Please restore SELinux context after creating the files in /var/lib/texmf

2018-06-03 Thread Norbert Preining
Hi Laurent, > 3) Copy the files instead of moving them, copied files ends with the > label of their parent folder I think I will implement this change upstream, so that other distributions will profit from it at the same time. Norbert -- PREINING Norbert

Bug#900580: Please restore SELinux context after creating the files in /var/lib/texmf

2018-06-02 Thread Hilmar Preuße
On 02.06.2018 13:48, Norbert Preining wrote: Hi, > Sure enough the kernel does, but based on a role set that is shipped > with Debian. I'm quite sure (near to 100%) that the kernel does not > contain rules about tetex!!! > > So the question is who/what did set up these rules, it was none of us.

Bug#900580: Please restore SELinux context after creating the files in /var/lib/texmf

2018-06-02 Thread Norbert Preining
Hi >> about the >>tetex_foobar >> stuff the SElinux ships out. This is nothing of my doing. So you need >to >> first find out who/what attaches any of these tags. >The kernel does. Sure enough the kernel does, but based on a role set that is shipped with Debian. I'm quite sure (near to

Bug#900580: Please restore SELinux context after creating the files in /var/lib/texmf

2018-06-02 Thread Laurent Bigonville
Le 02/06/18 à 02:08, Norbert Preining a écrit : On Fri, 01 Jun 2018, Laurent Bigonville wrote: Well the problem (from a SELinux) perspective is that the files from /var/lib/texmf are created in /tmp and the moved to their final location. So something needs to be done to fix that (as

Bug#900580: Please restore SELinux context after creating the files in /var/lib/texmf

2018-06-01 Thread Norbert Preining
On Fri, 01 Jun 2018, Laurent Bigonville wrote: > Well the problem (from a SELinux) perspective is that the files from > /var/lib/texmf are created in /tmp and the moved to their final location. > > So something needs to be done to fix that (as explained), so the first > question would be, what is

Bug#900580: Please restore SELinux context after creating the files in /var/lib/texmf

2018-06-01 Thread Laurent Bigonville
Le 01/06/18 à 18:08, Norbert Preining a écrit : Hi Laurent, sorry to say, but ... The generated files are ending being labeld as dpkg_script_tmp_t instead of tetex_data_t as they are created in /tmp and then moved. I have absolutely no idea what you are talking about!?! tetex_data_t is

Bug#900580: Please restore SELinux context after creating the files in /var/lib/texmf

2018-06-01 Thread Norbert Preining
Hi Laurent, sorry to say, but ... > The generated files are ending being labeld as dpkg_script_tmp_t instead > of tetex_data_t as they are created in /tmp and then moved. I have absolutely no idea what you are talking about!?! tetex_data_t is something I heard the very first time. It is

Bug#900580: Please restore SELinux context after creating the files in /var/lib/texmf

2018-06-01 Thread Laurent Bigonville
Package: tex-common Version: 6.09 Severity: normal User: selinux-de...@lists.alioth.debian.org Usertags: selinux Hi, When installing tex related packages, files are being generated in /var/lib/texmf by maintainer scripts/triggers The generated files are ending being labeld as dpkg_script_tmp_t