Curly Braces in Action Script not functioning (CIS RHEL6)

(imported topic written by kbrammer)

I am trying to get the CIS RHEL6 Baseline up and running in a test environment.

There are two tasks in the baseline. I am executing the task “RHEL6 Enterprise Deploy and Execute Scanning Scripts” which I understand is necessary for the fixlets to function. It errors.

So to get some sort of starting point on the troubleshooting, I run it in the action tab of the fixlet debugger, and I find that its erroring (in the debugger) on the following lines:

createfile until __EOF

{concatenations “%0a” of (values of headers “x-fixlet-detect-script0” of it) of fixlets of current site}

__EOF

I understand that the part of the script inside {curly braces} is relevance that executes and the result is substituted as text between the __EOF delimiters, and that that text becomes the __createfile, which gets written out in the next line of code. However, when I run that same line of code {inside the curly braces} on the Q&A tab of the fixlet debugger, it executes just fine and returns numerous lines of tagged fixlet data that seems correct.

And when I remove the {curly braces} from the action script, it also executes fine, predicitably populating the __createfile with the line of code (rather than the result of the line of code, as originally intended by the author).

So I’m scratching my head wondering how this could be? Do curly braces no longer function as they once did? Have they been replaced by something else? Or is there some sort of contextual difference between the Q&A tab and the Action tab of the Fixlet debugger? What am I missing or misunderstanding here?

(imported comment written by gearoid)

{ braces and so on work as they always did.

Try something like

createfile until _EOF

{names of sites}

_EOF

Your context difference could be the Evaulator - Local Client Evaluator vs. Local Fixlet Debugger Evaluator ? (Debug Menu -> Evaluate Using ->)

In QNA

// Local Fixlet Debugger

Q: ids of fixlets of current site

E: singular expression refers to nonexistent object.

// Local Client Evaluator

Q: ids of fixlets of current site

A: 1383 …

(imported comment written by JasonWalker)

In the Fixlet Debugger, the Action tab runs a little bit differently.

But even when run in “Local Client Evaluator” mode, I think the Fixlet Debugger simply isn’t going to have a context for “current site”. What should “current site” be in the debugger? “BES Support”? “Updates for Windows Applications”? See the problem there…

You could possibly do something like

fixlets of sites whose (name of it = “Enterprise Security”)

(And I would sure be interested in seeing what the QnA debugger decided was “current site” in gearoid’s results…)

(imported comment written by gearoid)

In qna tab using Local Client Evaluator the “current site” is
actionsite
, using Local Fixlet Debugger there’s no object.

On action tab I’ve no Local Client Evaulator option, using Local Fixlet Debugger throws a Substitution failed.