Thank you for the much needed clarification.  By the way, for allowconnects, 
allowallconnects, trustkeysfrom and skipverify, the CF3 Reference Manual 
mentions only that a regex match will be performed.  admit is documented fully.


On Feb 19, 2012, at 7:35 AM, Diego Zamboni wrote:

> Hi Abid,
> 
> The allowconnects, allowallconnects, admit, trustkeysfrom, and skipverify 
> attributes all accept both CIDR notation and regular expressions, and will do 
> the correct thing.
> 
> --Diego
> 
> 
> On Feb 17, 2012, at 6:32 AM, Abid Khwaja wrote:
> 
>> Today I begin the conversion of our CF2 environment to CF3.
>> 
>> Some basic questions I would like clarification on please.  In the below:
>> 
>>      allowconnects         => { "127.0.0.1" , "::1", @(def.acl) };
>> 
>> Each of the 3 items within brackets are regex’s.  But, at an examples CF3 
>> code site, I see this:
>> 
>>      
>> allowconnects       => { "10.1.16.0/20" };
>> 
>> If I understand this correctly, the above statement will not work as 
>> intended because the regex will only match the string “10.1.16.0/20”.  Is 
>> this correct?
>> 
>> Also, where are the values for @(def.acl) coming from?
>> _______________________________________________
>> Help-cfengine mailing list
>> Help-cfengine@cfengine.org
>> https://cfengine.org/mailman/listinfo/help-cfengine
> 

_______________________________________________
Help-cfengine mailing list
Help-cfengine@cfengine.org
https://cfengine.org/mailman/listinfo/help-cfengine

Reply via email to