[MJARSIGNER-26] Jar Signer does not support protected authentication path

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.2
• Fix Version/s: 1.3
• Flags: Patch
• Assignee: Tony Chemit
• Reporter: Michael Gruebsch
• Created: 11/Feb/13 09:03
• Updated: 06/Apr/15 01:16
• Resolved: 13/Nov/13 15:39

Description

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.

Issue Links

• depends upon: MSHARED-303 Jar Signer does not support protected authentication path
• depends upon: MJARSIGNER-27 Use maven-jarsigner 1.3