Forum: CFEngine Help
Subject: Re: allowconnects matching clarification needed
Author: real23
Link to topic: https://cfengine.com/forum/read.php?3,24897,24940#msg-24940
thanks
___
Help-cfengine mailing list
Help-cfengine@cfengine.org
https
I can remember from the past that CIDR notation produced a lot of errors. Is
this solved in newer versions of cfengine?
{{{
Protocol transaction broken off (1)
!!! System reports error for recv: "Connection reset by peer"
I: Made in version '1.3.0' of '/var/lib/cfengine3/inputs/bundles/ssh.cf'
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,
>
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
Forum: CFEngine Help
Subject: Re: allowconnects matching clarification needed
Author: neilhwatson
Link to topic: https://cfengine.com/forum/read.php?3,24897,24903#msg-24903
@(def.acl) comes from the common bundle named 'def'.
___
Help-cfengi
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
