JDK-8273646 : Add openssl from path variable also in to Default System Openssl Path in OpensslArtifactFetcher
  • Type: Bug
  • Component: security-libs
  • Sub-Component: java.security
  • Affected Version: 18
  • Priority: P4
  • Status: Resolved
  • Resolution: Fixed
  • OS: generic
  • CPU: generic
  • Submitted: 2021-09-13
  • Updated: 2021-10-09
  • Resolved: 2021-09-21
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
JDK 11 JDK 17 JDK 18 JDK 8
11.0.14-oracleFixed 17.0.2Fixed 18 b16Fixed 8u321Fixed
Related Reports
Relates :  
JDK-8266182 - Automate manual steps listed in the test jdk/sun/security/pkcs12/ParamsTest.java
Description
Right now OpensslArtifactFetcher invokes openssl from one of the following 2 absolute paths (in that order):

/usr/bin/openssl
/usr/local/bin/openssl

However, on some systems, especially Cygwin-based windows machines, the openssl may not necessarily be found on those paths. The test fails on such machines even though a valid openssl installation exists.

Consider adding a default openssl invocation without any absolute path specification.
Comments
Fix request [11u] I backport this for parity with 11.0.14-oracle. No risk, only a test change. Clean backport.
09-10-2021
17u fix request: Please approve this to backport to 17u.The patch applies clean, and the tests pass.
21-09-2021
Changeset: a5108a60 Author: Thejasvi Voniadka <tvoniadka@openjdk.org> Committer: Abdul Kolarkunnu <akolarkunnu@openjdk.org> Date: 2021-09-21 09:01:09 +0000 URL: https://git.openjdk.java.net/jdk/commit/a5108a605e6a1e427d90dbeeb8630a3d01d6b405
21-09-2021
[~weijun], we have had issues with this test on some of our test machines, especially windows. I have now updated the bug description to describe it better. I have now tested a patch on one such windows machines, and it seems to be adding value - instead of skipping openssl execution, it is now able to pick up the default-path openssl on that machine. Since the patch is simple, hope this is ok to go forward with..
15-09-2021
How necessary is this?
13-09-2021