Re: Because it's still a module?
“actually have no problems with it remaining as a module, either official or unofficial, but there are only a very limited number of scenarios I can see where having it actually compiled in the kernel will benefit users or administrators.”
Agree - but want to add one circumstance where it would have helped me on a client project in the past. Would not need to compiled on, but if something was official (in tree) module, it could be described as an OS option to be used, not as an external thing to be added. The first would be approved, the second automatically triggered review by the insecurity team, invariably resulting in four or five pages of reasons for considering anything risky - reasons that usually equated to “we didnt think of it therefore it must be bad” .....
Biting the hand that feeds IT
