dash.obfuscate.pattern

This configuration parameter enables you to hide sensitive information in the standard output (stdout) in audit results by using patterns to define the hidden information.

Beginning with release 2015.1, each pattern that you create must be embedded inside double quote characters (“). For example:

“nnnn-nnnn-nnnn-nnnn”

If there is a delay in the display of standard output information that you have designated to be hidden by defining a pattern, the agent may not recognize the pattern, and the information may be shown. To avoid delays, your obfuscation string should not exceed the size of the Cdash standard output buffer, which is 4KB.

In releases earlier than 2015.1, patterns could be embedded inside double quote characters (“) or slash characters (/). If slash characters were used, they are converted automatically to double quote characters when you upgrade from 2015 to 2015.1.

Each single character in a pattern corresponds to one character in actual session data.

Supported characters in a pattern are as follows:

a	Any lower case letter.
A	Any upper case letter.
d	Any character.
D	Any letter.
n	Any decimal digit character.
s	Symbols, such as the following: ~ ` ! @ # $ % ^ & * ( - _ = + [ { ] } | \ : ; ' < , > . ? /
-	Separator for exact matching in session data.
_	Separator for exact matching in session data.
(	Separator for exact matching in session data.
)	Separator for exact matching in session data.
,	Separator for exact matching in session data.
.	Separator for exact matching in session data.

If you define more than one pattern, separate the patterns with spaces. For example:

“nnnn-nnnn” “A-nnnn”

By default, this parameter does not contain any patterns.