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
As per discussion in: #461 (comment) and especially because of the security sensitive nature of rules.conf, please clarify the exact semantics of comments in it.
I.e., is it just if there's only leading whitespace before the #?
Is generally everything after a # (and including that) ignored (i.e. "end of line comments"), and if so, what if the # appears in some value of a rule, e.g. a USB device name, or is there some kind of detection whether it's part of a value?
Thanks,
Chris.
The text was updated successfully, but these errors were encountered:
Everything after the "#" symbol until the end of the line is treated as a comment if and only if the line starts with that particular symbol or has at least one leading whitespace character before the "#". The only exception is when it's part of the rule between quotation marks, e.g. part of the device name. However, not all fields of a rule can contain a "#" symbol, e.g. the device ID must have a format of XXXX:YYYY. I think there is nothing wrong with that.
Hey.
As per discussion in: #461 (comment) and especially because of the security sensitive nature of
rules.conf
, please clarify the exact semantics of comments in it.I.e., is it just if there's only leading whitespace before the
#
?Is generally everything after a
#
(and including that) ignored (i.e. "end of line comments"), and if so, what if the#
appears in some value of a rule, e.g. a USB device name, or is there some kind of detection whether it's part of a value?Thanks,
Chris.
The text was updated successfully, but these errors were encountered: