<div dir="ltr"><div style="font-family:arial,sans-serif;font-size:13px">Francisco, Shawn,</div><div style="font-family:arial,sans-serif;font-size:13px"><br></div><div style="font-family:arial,sans-serif;font-size:13px">What was your thinking behind the common-fix elements?</div>
<div style="font-family:arial,sans-serif;font-size:13px">Please also see (shortly) my new patches for fix insertion.</div><div style="font-family:arial,sans-serif;font-size:13px">I've re-written the fix insertion stuff. So that people can "declare" their use of particular environment variables in bash (using a bash function).</div>
<div style="font-family:arial,sans-serif;font-size:13px"><br></div><div style="font-family:arial,sans-serif;font-size:13px">Then the reworked combinefixes.py will pick up on the declaration and assign an XCCDF <sub idref/> to that variable. <sub idref/> is how oscap supports inserting particular values inside a fix. </div>
<div style="font-family:arial,sans-serif;font-size:13px"><br></div><div style="font-family:arial,sans-serif;font-size:13px">For unit testing (still incomplete), the bash function "needs" should grab the right value from XCCDF and populate it accordingly.</div>
<div style="font-family:arial,sans-serif;font-size:13px"><br></div><div style="font-family:arial,sans-serif;font-size:13px">Do we still need the fix-common elements, to insert them into the XCCDF?</div><div style="font-family:arial,sans-serif;font-size:13px">
I like to delete unused code.</div><div style="font-family:arial,sans-serif;font-size:13px"><br></div><div style="font-family:arial,sans-serif;font-size:13px">Jeff</div></div>