[Ndn-interest] How to add the SecRuleRelative Rules in validator-regex?
chengy.fan at gmail.com
Mon Mar 2 08:48:49 PST 2015
Thanks for the reply.
Further questions in line.
On Sat, Feb 28, 2015 at 4:45 PM, Alex Afanasyev <
alexander.afanasyev at ucla.edu> wrote:
> Hi Chengyu,
> I assumed there is a documentation for this method, but the commit that
> adds it is not yet merged. Here is the description we will have soon:
> * @brief Construct the rule
> * @param packetRegex regular expression to match the packet name that
> is qualified for the
> * the rule (e.g., `^(<.*>)$`)
> * @param signerRegex regular expression to match the the KeyLocator of
> the packet (e.g.,
> * `^(<.*>)<KEY>(<.*>)<ID-CERT><>$`)
> * @param comparator Defines the way expanded signer's name is matched
> against expanded
> * packet's name. Possible values are:
> * - "is-prefix-of"
> * - "is-strict-prefix-of"
> * - "equal"
Which symbol refers to which value?
> * @param packetExpand Expansion rule for packet's name (e.g., `\1`)
> * @param signerExpand Expansion rule for signer's name (e.g., `\1\2`)
> * @param isPositive flag denoting whether the rule is positive or
> * @note A packet complies with the rule only if both \p packetRegex
> matches the packet name
> * and \p signerRegex matches the KeyLocator name
According to the comparator description, I think this function also needs
to test if the expanded signer's name matched against the expanded packet's
> On Feb 27, 2015, at 7:59 PM, Chengyu Fan <chengy.fan at gmail.com> wrote:
> Could you tell me how the SecRuleRelative Rule works?
> Specifically, what's the meaning of each parameter? What conditions the
> rule will test to make a incoming data satisfy the rule?
> (const std::string & dataRegex,const std::string & signerRegex,const
> std::string & op,const std::string & dataExpand,const std::string &
> signerExpand,bool isPositive )
> On Fri, Feb 27, 2015 at 1:59 PM, Alex Afanasyev <
> alexander.afanasyev at ucla.edu> wrote:
>> On Feb 27, 2015, at 12:10 PM, Chengyu Fan <chengy.fan at gmail.com> wrote:
>> I'm trying to use the validator-regex to validate the incoming data, but
>> I stuck at how to add the SecRuleRelative Rule.
>> Can somebody tell me some clues?
>> Specifically, I find the example in SecurityLibrary(
>> but I don't understand the RuleRelative rule below ...
>> SecRuleRelative rule("^(<>*)$", "^([^<KEY>]*)<KEY>(<>*)<ksk-.*><ID-CERT>$",
>> ">", "\\1", "\\1\\2", true);
>> What's the meaning of ">", "\\1", "\\1\\2" ? Can someone give me an
>> This is just a regular expression rules. \\1 (\1, it’s just \ needs to
>> be escaped in c++) refer to th first group of the regular expression, \\2 refer
>> to the second group, etc.
>> There are many documentation sources about regexps, e.g.,
>> The only difference in our regular expressions is the fact that it is
>> defined over name components, not just strings. There is a documentation
>> for this at
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Ndn-interest