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/cd816250-564c-4b33-8937-27db667005dc%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to