19 Dub
2018
19 Dub
'18
15:46
On 2018-04-19 13:19, Martin Sehnoutka wrote:
On 04/19/2018 12:19 PM, Tomas Krizek wrote:
The bugs have been fixed in selinux-policy-3.13.1-283.26.fc27. Even
newer version of selinux-policy is available from F27 updates repo.
It is inadvisable to turn off SELinux, but it does work even with the
old selinux-policy when you issue `getenforce 0` and start the service.
I've tested this on a clean VM with out of the box installation of
knot-resolver.
--
Tomas Krizek
PGP: 4A8B A48C 2AED 933B D495 C509 A1FB A5F7 EF8C 4869
$ dnf update selinux-policy
It is still in testing. Anyway I tried to turn off SELinux, but the
result was the same. Isn't it supposed to work in that case?