Hi Neil,
Well I did this policy:
"$(sys.workdir)/ppkeys/root-.pub"
comment => "Clean up the bad ppkey copy",
handle => "ppkey_garbage",
delete => tidy,
classes => update_repaired("garbage_ppkey");
I was one of the initial folks effected by this root-.pub key issue.
So far I moved 40 of 200 machines over to the 3.1.2 but thought before
I get to far maybe it was better to wait till 3.1.4 but todays testing
has that delayed too.
I am not sure how to manage selected bugs in releases other then work
around in configurations. My environment starts with 200 but this is
really the start of a much larger adoption area so bug fixing without
major updates would be nice to work into a deployment plan? Sounds
like a great special topics paper. :-)
Gusto
On Tue, Feb 1, 2011 at 9:48 AM, <no-re...@cfengine.com> wrote:
> Forum: Cfengine Help
> Subject: Re: Cfengine 3.1.4 is released
> Author: neilhwatson
> Link to topic: https://cfengine.com/forum/read.php?3,20344,20385#msg-20385
>
>> Reading and writing of key name "root-.pub" eliminated (bug #442, #453).
>
> When one runs into this bug how can it be worked around without upgrading?
>
> _______________________________________________
> 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
