I'd like to bump this. I get wanting to not build them by default. It's still valid and useful content though and I think makes sense to have available as an advanced off-by-default developer-enabled feature. So I did just that: https://github.com/ComplianceAsCode/content/pull/4923 . Consequently the PR was promptly closed within about 20m by one of the maintainers with nothing more than a "Nope, not gonna do that", which, tbh, seemed like a fairly hostile way to interact with contributors. No discussion or explanation, just a sprinkling of nist references that don't actually have to do with the specific issue. The content generation used the enable_derivatives script which already peppers the XCCDF with applicable warnings.

----------
Chuck Atkins
Staff R&D Engineer, Scientific Computing
Kitware, Inc.
(518) 881-1183

On Fri, Aug 9, 2019 at 12:34 AM Tim Burress <taj@fedoraproject.org> wrote:

> There's really zero excuse for continued use of CentOS, especially for
> Government systems.

Honestly we would probably use RHEL for our servers if we could afford it, simply because it would be one less thing to worry about, but for a small company that nevertheless has lots of servers, the cost, or at least what we were quoted, was prohibitive. Actually even using CentOS required a cultural adjustment. Before that we built the OS ourselves from source code.
_______________________________________________
scap-security-guide mailing list -- scap-security-guide@lists.fedorahosted.org
To unsubscribe send an email to scap-security-guide-leave@lists.fedorahosted.org
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedorahosted.org/archives/list/scap-security-guide@lists.fedorahosted.org