maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tony Chemit (JIRA)" <j...@codehaus.org>
Subject [jira] (MJARSIGNER-21) jars signed using Java 7 have "invalid SHA1 signature"
Date Sat, 28 Dec 2013 15:02:45 GMT

    [ https://jira.codehaus.org/browse/MJARSIGNER-21?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=337896#comment-337896
] 

Tony Chemit edited comment on MJARSIGNER-21 at 12/28/13 9:00 AM:
-----------------------------------------------------------------

FMU, there is no need to specify the digest algo. Just cleaning the manifest while unsigning
a jar befoire resign it should be sufficent. See MSHARED-314
                
      was (Author: tchemit):
    FMU, there is no need to specify the digest algo. Just cleaning the manifest while unsigning
a jar befoire resign it should be sufficent. See MSHARE-314
                  
> jars signed using Java 7 have "invalid SHA1 signature"
> ------------------------------------------------------
>
>                 Key: MJARSIGNER-21
>                 URL: https://jira.codehaus.org/browse/MJARSIGNER-21
>             Project: Maven Jar Signer Plugin
>          Issue Type: Bug
>    Affects Versions: 1.2
>         Environment: Java 7, Maven 2.2.1
>            Reporter: Mike Calmus
>            Assignee: Tony Chemit
>            Priority: Critical
>
> Using the plugin with Java 6 works fine. When I use it with Java 7, my applet won't load
because the SHA1 signatures are invalid.

--
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

Mime
View raw message