Re: selinux and debian squeeze 9.5
> > squeeze! > > Speaking of obvious — the OP says 9.5, so presumably they _meant_ to say > Stretch — no? It does not say "9.5" anywhere in the original post. It does, however, say 9.5 in the Subject header. Unfortunately, we have a divide here. Newbies think that putting information in the Subject header is actually a good idea, that people will read it, and even worse, that if information is in the Subject, it does not need to be repeated in the body. Veterans don't read Subject headers at all. So we see only the word "squeeze", and you get that reaction. We've been conditioned over several decades to ignore Subject headers because they are meaningless noise. Occasionally we may have to use one as a reference in order to find a thread in a web-based archive. In that case, the Subject header is like a message ID string. It's just randomly generated characters with no semantic meaning. We don't read banners on the tops of web pages, either. We've been conditioned to learn that banners are advertisements, and therefore we do not look at them. (Which is why that green inserted "Download Debian 9.5" button in the banner on https://www.debian.org/ is a horribly bad design. Nobody will see it. Because it's inside a web page banner.)
correction, stretch 9.5 Re: selinux and debian squeeze 9.5
On 11/3/18 7:45 PM, Mark Fletcher wrote: > > squeeze! You could be very lucky and someone with the same outdated, > no longer supported distribution and experiencing the same problem > comes along. I wouldn't count on it though. > > > Any suggestions? > > The obvious. > > > Speaking of obvious — the OP says 9.5, so presumably they _meant_ to > say Stretch — no? Indeed, I did mistype. Stretch.
Re: selinux and debian squeeze 9.5
> squeeze! You could be very lucky and someone with the same outdated, > no longer supported distribution and experiencing the same problem > comes along. I wouldn't count on it though. > > > Any suggestions? > > The obvious. > Speaking of obvious — the OP says 9.5, so presumably they _meant_ to say Stretch — no? Mark
Re: selinux and debian squeeze 9.5
On Sat 03 Nov 2018 at 18:04:49 -0400, John Jasen wrote: > For some reason, my attempts at enabling SELinux on a squeeze system > just aren't taking. > > As I understand it, the following steps are required: > > a) installing selinux-policy-default and dependencies > > b) editing /etc/selinux/config to select default policy and permissive > or enforcing. > > c) adding security=selinux to the grub boot line. > > d) ensuring the filesystem selinux contexts are relabeled on reboot > (touch /.autorelabel) > > > However, for one particular test system, when it comes back up, SELinux > is disabled, and dmesg does not show SELinux in the kernel option line. > I feel like I'm missing something obvious, here. squeeze! You could be very lucky and someone with the same outdated, no longer supported distribution and experiencing the same problem comes along. I wouldn't count on it though. > Any suggestions? The obvious. -- Brian.
selinux and debian squeeze 9.5
For some reason, my attempts at enabling SELinux on a squeeze system just aren't taking. As I understand it, the following steps are required: a) installing selinux-policy-default and dependencies b) editing /etc/selinux/config to select default policy and permissive or enforcing. c) adding security=selinux to the grub boot line. d) ensuring the filesystem selinux contexts are relabeled on reboot (touch /.autorelabel) However, for one particular test system, when it comes back up, SELinux is disabled, and dmesg does not show SELinux in the kernel option line. I feel like I'm missing something obvious, here. Any suggestions?
selinux and debian squeeze 9.5
For some reason, my attempts at enabling SELinux on a squeeze system just aren't taking. As I understand it, the following steps are required: a) installing selinux-policy-default and dependencies b) editing /etc/selinux/config to select default policy and permissive or enforcing. c) adding security=selinux to the grub boot line. d) ensuring the filesystem selinux contexts are relabeled on reboot (touch /.autorelabel) However, for one particular test system, when it comes back up, SELinux is disabled, and dmesg does not show SELinux in the kernel option line. I feel like I'm missing something obvious, here. Any suggestions?
