On Tuesday, 12 January 2021 2:23:47 AM AEDT Dominick Grift wrote: > > I'm looking to remove modules for dead programs, such as hal and > > consolekit. The question is how long to keep modules for dead > > programs? I'm thinking something like 3-5 years. > > Agree I think we should drop them when the programs aren't in the latest DEVELOPMENT versions of Fedora, Debian, or any other distribution that supports SE Linux. The new policy will only be used by new versions of those distributions. Running a newer version of policy on an older version will not provide any benefits and in some cases won't work properly. People should NOT expect the Git refpolicy to work well on Debian/Buster, if they try it they shouldn't expect much help from me. While I have a general aim that you should be able to upgrade kernel, SE Linux policy (and things that get dragged in with it like libc), and applications separately this isn't a guarantee. If Debian/ Unstable doesn't include a daemon then I have no interest in supporting that daemon with SE Linux policy in Debian/Unstable. People can migrate their configuration to the replacement daemon as part of the process of upgrading SE Linux policy. Distributions like Fedora have a stronger binding between policy and daemons than Debian does, and RHEL has an even stronger binding. That said, Debian tends to keep daemons longer than most distributions. If a daemon doesn't have known security issues and some people like using it then it stays in the archive. When Debian keeps a daemon that loses support upstream your REALLY want good SE Linux policy for it! > some suggestions: > > sectoolm, kdumpgui, kudzu, readahead, smoltclient, tmpreaper, > firewallgui, gift, podsleuth, ptchown, sambagui, yam, hotplug, pcmcia, > dnssectrigger, kerneloops, keyboardd, rhgb, roundup, speedtouch, w3c, > xprint kerneloops is still in Debian/Unstable and running on some of my Debian/ Unstable machines. In Debian/Unstable /etc/init.d/mountnfs-bootclean.sh has type tmpreaper_exec_t, so this is still being used. But I am up for a discussion about other ways of doing this. -- My Main Blog http://etbe.coker.com.au/ My Documents Blog http://doc.coker.com.au/
