I had no problem at all, it went all flawlessly, the agent taking care of the keys migration. Tested on Debian 4 and 5, Centos 4 and 5, and Windows
Nicolas CHARLES Normation SAS - http://www.normation.com 44 rue Cauchy – 94110 ARCUEIL +33 (0)1 83 62 26 96 - +33 (0)6 14 63 25 18 On 10/01/2011 18:28, Gusto wrote: > Hi Folks, > > I have a ppkeys question: Has anyone had issues with 3.0.4/3.0.5p1 > generated keys and the new 3.1.2 keys updates? Does the 3.1.0+ new > hash change the key so the server's public copy of the client no > longer matches? Ideally I am going to move everything just was looking > for others experiences... > > I have an established environment with 200+ machines which has grown > from 3.0.1 and is mostly at 3.0.5p1 at this point. I am testing the > update to the 3.1.2 on the clients (servers still at 3.0.5p1) but I > see some key issues preventing me from just making a large update. > > My current solution is to just removing the old keys from client and > server then run cf-key to get things working again. When we commit to > the update first to update are the main policy servers then the > clients. Ideally I would like to just update the binaries leaving keys > in place if possible. Before taking the 3.1.2 plunge I wanted to ask > if anyone has done similar site updates? > > Best Regards, > Gusto > _______________________________________________ > 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
