You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 2, 2024. It is now read-only.
For example given the input glob pattern would be '\*' then the resulting Perl 5's regular
expression would be '^\\.*$' in the default (glob_noescape=false) case (here '\' would be
interpreted as an escape character), and would produce '^\.*$' in glob_noescape=true case
(since here '\' would be interpreted as an literal). Similarly the output for '\?' glob
pattern would be '^\\.$' (default, glob_noescape=false case), and '^\.$' for
glob_noescape=true case.
As correctly pointed out by David via the link above, the resulting form of examples is incorrect now.
The correct version should be:
# Results for C '\*' glob:
----------------------------------------
glob_noescape | Perl regular expression
----------------------------------------
FALSE | ^\*$
TRUE | ^\\.*$
----------------------------------------
# Results for C '\?' glob:
----------------------------------------
glob_noescape | Perl regular expression
----------------------------------------
FALSE | ^\?$
TRUE | ^\\.$
----------------------------------------
And to provide yet one example for handling of '[' and ']' characters it's listed below:
# Results for C '\[hello\]' glob:
----------------------------------------
glob_noescape | Perl regular expression
----------------------------------------
FALSE | ^\[hello\]$
TRUE | ^\\[hello\\]$
I will create & attach corresponding OVAL Language git repository changes & add a diff here.
See http://making-security-measurable.1364806.n2.nabble.com/Error-in-the-schema-documentation-for-GlobToRegexFunctionType-td7586183.html#a7586394
The text was updated successfully, but these errors were encountered: