This is the bug corresponding to Issue 17128. We need a new codesigning certificate.
Fixed in 30705. Note that the new certicate is SHA-256 rather than SHA-1. The tester should test: * Windows client installer on common Windows versions. * The Java client verifier.
*** Bug 5624 has been marked as a duplicate of this bug. ***
From 5624: "With bug 5468, certificates was moved to ctc/pki and while testing that bug i noticed there was no info about how to update."
(In reply to comment #3) > From 5624: > > "With bug 5468, certificates was moved to ctc/pki and while testing that bug i > noticed there was no info about how to update." Fixed in 30733.
(In reply to comment #1) > Fixed in 30705. Note that the new certicate is SHA-256 rather than SHA-1. The > tester should test: > > * Windows client installer on common Windows versions. > Verified that the new certificate was used for signing the installer.
(In reply to comment #1) > Fixed in 30705. Note that the new certicate is SHA-256 rather than SHA-1. The > tester should test: > > * Windows client installer on common Windows versions. > > * The Java client verifier. Verified that the new certificate was used to sign files in ThinLincClientVerifier.jar: jarsigner -verify -certs -verbose ThinLincClientVerifier.jar
(In reply to comment #4) > (In reply to comment #3) > > From 5624: > > > > "With bug 5468, certificates was moved to ctc/pki and while testing that bug i > > noticed there was no info about how to update." > > Fixed in 30733. There is no information about the apple certificate except that one exists... Also the text describing GoDaddy cert usage for signing Windows stuff is not true, the ThinLincClientVerifier.jar file not just windows... Maybe rephrase like: One from GoDaddy, used for normal code signing
Looks good. Closing.