[
https://jira.codehaus.org/browse/MSHARED-303?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tony Chemit closed MSHARED-303.
-------------------------------
Resolution: Fixed
Fix Version/s: maven-jarsigner-1.2
> Jar Signer does not support protected authentication path
> ---------------------------------------------------------
>
> Key: MSHARED-303
> URL: https://jira.codehaus.org/browse/MSHARED-303
> Project: Maven Shared Components
> Issue Type: Task
> Affects Versions: maven-jarsigner-1.0, maven-jarsigner-1.1
> Reporter: Tony Chemit
> Assignee: Tony Chemit
> Fix For: maven-jarsigner-1.2
>
>
> The jarsigner tool has an option "-protected" (see
> http://docs.oracle.com/javase/6/docs/technotes/tools/windows/jarsigner.html#Options,
> documentation for option -storetype): a PCKS#11 token may have a protected
> authentication path (such as a dedicated PIN-pad or a biometric reader). In
> such case the -protected option must be specified and no password options can
> be specified.
> The current version does not support this option. Please find patches for
> maven-jarsigner-1.0 and maven-jarsigner-plugin (Version 1.3-SNAPSHOT)
> attached.
> Testcases are left out because a pin reader, a PCKS#11 smart card and human
> interaction would be necessary to test this scenario. However, the patched
> version works fine in my environment.
--
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
