You are viewing a plain text version of this content. The canonical link for it is here.
Posted to infrastructure-issues@apache.org by "Maxim Solodovnik (JIRA)" <ji...@apache.org> on 2016/07/27 04:06:20 UTC
[jira] [Created] (INFRA-12336) "Invalid signature file digest for
Manifest main attributes" after signing
Maxim Solodovnik created INFRA-12336:
----------------------------------------
Summary: "Invalid signature file digest for Manifest main attributes" after signing
Key: INFRA-12336
URL: https://issues.apache.org/jira/browse/INFRA-12336
Project: Infrastructure
Issue Type: Bug
Components: Codesigning
Reporter: Maxim Solodovnik
I'm trying to release Apache Openmeetings.
We using symantec codesigning to sign distributed Java Web Start application.
It contains bcprov-jdk15on-1.54.jar
According to the FAQ [1] to "use signed jars (such as JCE extensions)" I "can multiply sign the jar, adding code signing certificates over another existing certificate chain"
and it works as expected in our nightly builds using self-signed certificates.
Unfortunately I got
"Unable to load resource"
"Invalid signature file digest for Manifest main attributes"
After signing using Symantec service
Would appreciate if you can fix it ASAP
Our build/sign instructions are here [2]
[1] https://docs.oracle.com/javase/8/docs/technotes/guides/javaws/developersguide/faq.html#s221
[2] http://openmeetings.apache.org/ReleaseGuide.html
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)