Jenkins master is hosted on Windows server 2012 and I am trying installing slave on separate Windows Server 2012
On Tuesday, March 8, 2016 at 6:21:26 PM UTC, Prashant Sawant wrote: > > Hi There , > I am facing same issue ... my slave,jar and remoting.jar are both on 2.52 > , still it's giving me security issue > can you please advice > > Thanks > Prashant > > On Wednesday, July 22, 2015 at 7:33:06 PM UTC+1, Kohsuke Kawaguchi wrote: >> >> Yes, my code signing certificate expired. >> >> Up until about 2 years ago, I was signing these bits without including >> the timestamp. That has the unfortunate side effect of invalidating the >> signature when my certificate expires, which happens sooner or later. >> >> Since then I have modified the signing process to include the timestamp, >> so that the signed & release bits will continue to pass the signature test >> even when a certificate expires. That happened about 2 years ago. You are >> running a fairly old version, so I suspect you ae running an affected >> version. That said, 1.554.3 has slave jar 2.36, which should have the >> timestamp. Are you sure your slave.jar is up-to-date against the master? >> Can you look at the slave manifest to see the version number? >> >> I recommend you ugprade Jenkins altogether, but to get unblocked quickly, >> just download the latest slave.jar from here >> <http://repo.jenkins-ci.org/releases/org/jenkins-ci/main/remoting/> and >> use it as the slave.jar. >> >> >> On Wednesday, July 22, 2015 at 11:16:43 AM UTC-7, Dunnigan, Terrence J >> wrote: >>> >>> Has anyone else encountered this? >>> >>> >>> >>> We’re running Jenkins LTS 1.554.3 and Java Server SDK 7u72 on a Windows >>> 2008 Server, and Java 7u72 on the slave workstations. When we restarted our >>> server yesterday none of our slaves connected via DCOM. They never made it >>> past the first (Connecting to …) or second (Checking for Java) step. >>> >>> >>> >>> At the same time, I’m now seeing Java security warnings on the slaves >>> when running the Jenkins Remoting Agent. The code signing certificate >>> expired just a few days ago (7/18). Could this be related to my DCOM errors? >>> >>> >>> >>> >>> >>> Terry >>> >> -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/0d8d2ce5-1241-49ba-a8ed-22a28feee871%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
