[JIRA] [core] (JENKINS-23310) Code signing certificate of winp.dll has expired
Torsten Schlabach edited a comment on JENKINS-23310 Code signing certificate of winp.dll has expired Yes, it has been fixed in the sense that we can indeed download 1.569 now. Though we will not be able to download 1.569 in some remote future point in time from now after the new code signing certificate will have expired again. BUT I learn from http://portableapps.com/node/24236 (the last remark by John T. Haller dated July 14, 2010 at 10:41am in that thread that the fault isn't with the Jenkins / Winp developers at all but with the people who implemented / configured the certificate checks on our content inspection HTTP proxy server. After reading, it sounds quite logical to me that a code signing certificate needs to be valid at the point in time the code is signed, not at the code in time I want to download or execute the code. Unless the certificate had been revoked in the meanwhile, but that doesn't seem to be the case here. So in other words, you didn't actually fix it neither by chance or purpose but it's just luck that when I tried to download 1.569 yesterday that I was still withing the time windows of validity of your code signing certificate despite that time window shouldn't matter at all for what I am trying to do. HTH This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-23310) Code signing certificate of winp.dll has expired
Torsten Schlabach commented on JENKINS-23310 Code signing certificate of winp.dll has expired Yes, it has been fixed in the sense that we can indeed download 1.569 now. Though we will not be able to download 1.569 in some remote future point in time from now after the new code signing certificate will have expired again. BUT I learn from http://portableapps.com/node/24236 (the last remark by John T. Haller dated July 14, 2010 at 10:41am in that thread that the fault isn't with the Jenkins / Winp developers at all but with the people who make the certificate checks. After reading, it sounds quite logical to me that a code signing certificate needs to be valid at the point in time the code is signed, not at the code in time I want to download or execute the code. Unless the certificate had been revoked in the meanwhile, but that doesn't seem to be the case here. So in other words, you didn't actually fix it neither by chance or purpose but it's just luck that when I tried to download 1.569 yesterday that I was still withing the time windows of validity of your code signing certificate despite that time window shouldn't matter at all for what I am trying to do. HTH This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-23310) Code signing certificate of winp.dll has expired
Torsten Schlabach edited a comment on JENKINS-23310 Code signing certificate of winp.dll has expired Yes, it has been fixed in the sense that we can indeed download 1.569 now. Though we will not be able to download 1.569 in some remote future point in time from now after the new code signing certificate will have expired again. BUT I learn from http://portableapps.com/node/24236 (the last remark by John T. Haller dated July 14, 2010 at 10:41am in that thread that the fault isn't with the Jenkins / Winp developers at all but with the people who implemented / configured the certificate checks on our content inspection HTTP proxy server. After reading, it sounds quite logical to me that a code signing certificate needs to be valid at the point in time the code is signed, not at the code in time I want to download or execute the code. Unless the certificate had been revoked in the meanwhile, but that doesn't seem to be the case here. So in other words, you didn't actually fix it neither by chance nor by purpose but it's just luck that when I tried to download 1.569 yesterday that I was still within the time window of validity of your code signing certificate, despite that time window shouldn't matter at all for my download. HTH This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-23310) Code signing certificate of winp.dll has expired
Torsten Schlabach resolved JENKINS-23310 as Not A Defect Code signing certificate of winp.dll has expired Change By: Torsten Schlabach (26/Jun/14 8:13 AM) Status: Open Resolved Resolution: NotADefect This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-23310) Code signing certificate of winp.dll has expired
Daniel Beck commented on JENKINS-23310 Code signing certificate of winp.dll has expired New Winp release was integrated for 1.569 (JENKINS-23410). Maybe the cert issue has been fixed. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-23310) Code signing certificate of winp.dll has expired
Daniel Beck updated JENKINS-23310 Code signing certificate of winp.dll has expired Reducing priority: Download of jenkins.war is hardly a production-breaking issue; and a workaround is available in downloading not through the proxy. All issues here are imposed by your own organization. Change By: Daniel Beck (10/Jun/14 12:19 PM) Priority: Blocker Major This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-23310) Code signing certificate of winp.dll has expired
Oleg Nenashev updated JENKINS-23310 Code signing certificate of winp.dll has expired Kohsuke is an owner of the WinP library project Change By: Oleg Nenashev (09/Jun/14 12:24 PM) Assignee: KohsukeKawaguchi This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-23310) Code signing certificate of winp.dll has expired
Torsten Schlabach created JENKINS-23310 Code signing certificate of winp.dll has expired Issue Type: Bug Assignee: Unassigned Components: core Created: 04/Jun/14 11:53 AM Description: We cannot download the jenkins.war through our HTTP proxy any more. Here is the error message: Grund der Blockierung: certificate has expired (depth = 0), revocation status unresolvable (depth = 0), revocation status unresolvable (depth = 1), revocation status unresolvable (depth = 2), revocation status unresolvable (depth = 3) Verletzung der Sicherheitsnorm in Datei: http://jenkins.mirror.isppower.de/war/1.566/jenkins.war/WEB-INF/lib/winp-1.19.jar/winp.dll Sorry for the German language parts, but I think the issue becomes clear. Project: Jenkins Priority: Blocker Reporter: Torsten Schlabach This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
