Bug 27289 - Java 11 : jarsigner cannot sign a jar
Summary: Java 11 : jarsigner cannot sign a jar
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: All Linux
Priority: Normal normal
Target Milestone: Mageia 8
Assignee: Java Stack Maintainers
QA Contact:
URL:
Whiteboard:
Keywords: Triaged
Depends on:
Blocks: 27270
  Show dependency tree / graph
 
Reported: 2020-09-18 16:32 CEST by Nicolas Salguero
Modified: 2020-09-20 09:16 CEST (History)
2 users (show)

See Also:
Source RPM: java-11-openjdk-11.0.9.2-0.0.ea.3.mga8.src.rpm
CVE:
Status comment:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Nicolas Salguero 2020-09-18 16:32:25 CEST 
Hi,

When trying to build tigervnc 1.11.0 (bug 27270), I discovered that jarsigner from java-11-openjdk-11.0.9.2-0.0.ea.3.mga8 is unable to sign a jar because the list of values of the property jdk.disabled.namedCurves contains some values with a space in their name, which causes the following error:
"""
Error in security property.
  Constraint unknown: c2tnb191v1
"""

Best regards,

Nico.
Nicolas Salguero 2020-09-18 16:33:08 CEST

Source RPM: (none) => java-11-openjdk-11.0.9.2-0.0.ea.3.mga8.src.rpm
Blocks: (none) => 27270

Comment 1 Frank Griffin 2020-09-18 16:55:31 CEST 
This may be related to bug#27165 which also may be a signing issue.

CC: (none) => ftg

Comment 2 Martin Whitaker 2020-09-18 16:56:33 CEST 
This may help: https://bugzilla.redhat.com/show_bug.cgi?id=1868074
Comment 3 Aurelien Oudelet 2020-09-18 18:18:26 CEST 
Hi, thanks for reporting this bug.
Assigned to the package maintainer group Java.

(Packager: Please set the status to 'assigned' if you are working on it)

Target Milestone: --- => Mageia 8
Assignee: bugsquad => java
Keywords: (none) => Triaged
CC: (none) => ouaurelien

Comment 4 Nicolas Salguero 2020-09-20 09:16:18 CEST 
Hi,

java-11-openjdk-11.0.9.6-0.0.ea.1.mga8 solves the issue.

Best regards,

Nico.

Resolution: (none) => FIXED
Status: NEW => RESOLVED
Note You need to log in before you can comment on or make changes to this bug.