There doesn't seem to be a way to add new prose (ie from the
SNAC
guide) to the scap-security-guide, due to issues with
well-formedness. File names, Linux keywords, and config file
settings are wrapped in<xhtml:code> and<xhtml:pre> tags in ssg, but
not in the SNAC guide, so anything that isn't well-formed within the
SNAC prose breaks the xccdf.
Right ... because it's not XCCDF. It's just a PDF rendering of
(logically-organized) LaTeX. (If I understand you correctly.)
XCCDF tags will need to be manually inserted. Copy and paste will not
be enough. You may see many of the tags on separate lines in the
source, since some of us are using vim for "convenient" line-oriented
manipulation/duplication of tags.
Best practice for authoring remains an open question. I'm fully aware
this is a compromise with pros/cons, and also aware of other approaches.
There are also some cases where these settings are well-formed, but
are still wrapped in the namespace (xhtml:code/pre) tags within the
scap-security-guide. I'd like to keep the SNAC+scap-sec-guide merge
consistent with the previous security-guide, but I can't seem to find
an all-encompassing set of conditions to systematically add these
tags where appropriate. I'm wondering if you guys know of a way to
do this (other than manually).
I was assuming it would be done manually, and that initial QA would be
done along the way.
We did some experimentation using plasTeX to convert the original SNAC
guide wholesale to XCCDF, but decided that manual copy-paste was
probably a better approach (and the original commits were actually from
the USGCB content for RHEL 5, which were of course derived from sections
in the SNAC guide).
If not, this would be great functionality to add for future use. If
no one else is currently doing so, I'd like to work on it.
I can share the plasTeX if you wanted to convert some LaTeX to XCCDF,
but let's chat offline to make sure I understand your goal. I'm not
totally sure this is something we really want done automatically.