Yes, this is very helpful -- thanks!
I've also just committed this to the project (in the references folder).
This will allow us to tag items for applicability/inclusion for RHEL 6
consensus (or document otherwise as we develop consensus).
Unless I'm missing something, I didn't see content yet for <fix>es,
though I see that <fixtext> is being used, while <description> is being
used to describe the motivation for the configuration action.
This is excellent, since we have an easy correspondence here with our
we've been using <description>, for what you use <fixtext>
we've been using <rationale>, for what you use <description>
A little XSLT could thus format scap-security-guide's content similarly
to STIG-looking content.
Thanks again for sharing.
On 06/04/2012 11:39 AM, Shawn Wells wrote:
On 6/4/12 9:17 AM, Mackanick, Jason W CIV (US) wrote:
> Attached is the draft RHEL5 content we are beginning to release to the
> field for testing.
I skimmed this and will spend more time on it, but I fully intend on
stealing your <fix>'s where relevant for the RHEL6 guide. Thanks for