RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1841943 - Man page for update-crypto-policies is incorrect with regards to Openjdk
Summary: Man page for update-crypto-policies is incorrect with regards to Openjdk
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: crypto-policies
Version: 8.2
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: rc
: 8.3
Assignee: Tomas Mraz
QA Contact: Ondrej Moriš
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-05-29 21:30 UTC by Chris Dolphy
Modified: 2020-11-04 02:01 UTC (History)
2 users (show)

Fixed In Version: crypto-policies-20200610-1.git0ac8b1f.el8
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-11-04 01:58:45 UTC
Type: Bug
Target Upstream Version:
Embargoed:
pm-rhel: mirror+

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2020:4536 0 None None None 2020-11-04 01:59:01 UTC

Description Chris Dolphy 2020-05-29 21:30:54 UTC 
Description of problem:
Man page for update-crypto-policies is incorrect with regards to Openjdk

The man page in the openjdk section says:
       Alternatively one can create a file containing the overridden values for
           jdk.tls.disabledAlgorithms, jdk.certpath.disabledAlgorithms and pass the location of that file to Java on the command line using the -Djava.security.properties=<path to file>.

But in fact this will not work because the crypto policies always takes precedence as it's loaded last.

However, there is another way to disable the crypto policies.  you can set the system property "java.security.disableSystemPropertiesFile" to true.

So my suggestion is change the man page to say:
       ·   Applications using Java: No special treatment is required. Applications using Java will load the crypto policies by default. These applications will then inherit the settings for allowed cipher
           suites, allowed TLS and DTLS protocol versions, allowed elliptic curves, and limits for cryptographic keys. To prevent openjdk applications from adhering to the policy the
           <java.home>/jre/lib/security/java.security file should be edited to contain security.useSystemPropertiesFile=false or the system property java.security.disableSystemPropertiesFile to "true".  Note that the system property java.security.properties is loaded with a lower preference than the crypto policies, so you can't use this property to override crypto policies without also preventing openjdk applications from adhering to the policy.


Version-Release number of selected component (if applicable):
RHEL 8.2

How reproducible:
very

Steps to Reproduce:
1. man update-crypto-policies 
2. get wrong info! 

Actual results:


Expected results:


Additional info:
Comment 5 Tomas Mraz 2020-06-03 08:51:54 UTC 
This was already fixed in 8.3 build by the upstream rebase.
Comment 6 Ondrej Moriš 2020-06-03 13:46:08 UTC 
Chris, man page was corrected as follows:

 Applications using Java: No special treatment is required. 
 Applications using Java will load the crypto policies by default. 
 These applications will then inherit the settings for allowed 
 cipher suites, allowed TLS and DTLS protocol versions, allowed 
 elliptic curves, and limits for cryptographic keys. To prevent 
 openjdk applications from adhering to the policy the 
 <java.home>/jre/lib/security/java.security file should be edited 
 to contain security.useSystemPropertiesFile=false. Alternatively 
 one can create a file containing the overridden values for 
 jdk.tls.disabledAlgorithms, jdk.certpath.disabledAlgorithms and
 pass the location of that file to Java on the command line using 
 the -Djava.security.properties=<path to file>.

Is that okay for you?
Comment 7 Tomas Mraz 2020-06-03 14:28:00 UTC 
Oh, I misread the description. The fix is not there yet.
Comment 9 Ondrej Moriš 2020-06-16 12:22:38 UTC 
Successfully verified.

# man update-crypto-policies
...
  . Applications using Java: No special treatment is required. Applications using Java will 
    load the crypto policies by default. These applications will then inherit the settings 
    for allowed cipher suites, allowed TLS and DTLS protocol versions, allowed elliptic curves,
    and limits for cryptographic keys. To prevent openjdk applications from adhering to the 
    policy the <java.home>/jre/lib/security/java.security file should be edited to contain
    security.useSystemPropertiesFile=false or the system property 
    java.security.disableSystemPropertiesFile be set to true. Note that the system property 
    java.security.properties is loaded with a lower preference than the crypto policies, so 
    you can’t use this property to override crypto policies without also preventing openjdk 
    applications from adhering to the policy.
Comment 12 errata-xmlrpc 2020-11-04 01:58:45 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (crypto-policies bug fix and enhancement update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2020:4536
Note You need to log in before you can comment on or make changes to this bug.