Bug #12548
closed
Java 9 / Java 10 compatibility: security exception for JS VM
Added by François ARMAND almost 6 years ago.
Updated almost 6 years ago.
Category:
Web - Maintenance
Description
Java 9/10 introduces new needed exceptions that must be specified, like it was in #12448. We really need to be able to specify them in a file out of rudder (#12450).
- Status changed from New to In progress
- Status changed from In progress to Pending technical review
- Assignee changed from François ARMAND to Vincent MEMBRÉ
- Pull Request set to https://github.com/Normation/rudder/pull/1920
- Subject changed from New security exception for JS vm with openJDK 10 to Java 9 / Java 10 compatibility: security exception for JS vm and jee dependency
- Description updated (diff)
- Category changed from Security to Web - Maintenance
- Status changed from Pending technical review to In progress
- Assignee changed from Vincent MEMBRÉ to François ARMAND
- Related to Bug #12450: JS sandbox permission must be defined in a file added
- Related to Bug #12448: Failed generation with "Could not initialize class javax.crypto.JceSecurity" added
- Subject changed from Java 9 / Java 10 compatibility: security exception for JS vm and jee dependency to Java 9 / Java 10 compatibility: security exception for JS VM
- Status changed from In progress to Pending technical review
- Assignee changed from François ARMAND to Vincent MEMBRÉ
- Description updated (diff)
- Related to Bug #12557: Java 9 / Java 10 compatibility: javax/xml/bind removed added
- Status changed from Pending technical review to Pending release
- Status changed from Pending release to Released
This bug has been fixed in Rudder 4.1.12, 4.2.6 and 4.3.1 which were released today.
Also available in: Atom
PDF
Updated by 
Updated by