OPERATIONAL DEFECT DATABASE
...
...
On an HPE ProLiant server with HPE Integrated Lights-Out 3 (iLO 3) firmware version 1.90 (or earlier) using Java 8 update 171 (or later), when attempting to launch Java IRC via Web Start when AES/3DES encryption is disabled (default setting.), a Java exception error will occur.
Any HPE ProLiant server with HPE Integrated Lights-Out 3 (iLO 3) firmware version 1.90 (or earlier) using Java 8 update 171 (or later).
In order to launch Java IRC on iLO3 firmware version 1.90 (or earlier) using Java 8 update 171, perform either of the following: Enable "Enforce AES/3DES Encryption" in the Security-Encryption Settings of iLO webpage. OR Remove "3DES_EDE_CBC" from disabled list of client JDK cipher suites. 3DES cipher suites are disabled in Java 8 update 171 via the jdk.tls.disabledAlgorithms Security Property. NOTE: Products sold prior to the November 1, 2015 separation of Hewlett-Packard Company into Hewlett Packard Enterprise Company and HP Inc. may have older product names and model numbers that differ from current models. RECEIVE PROACTIVE UPDATES : Receive support alerts (such as Customer Advisories), as well as updates on drivers, software, firmware, and customer replaceable components, proactively via e-mail through HPE Subscriber's Choice. Sign up for Subscriber's Choice at the following URL: Proactive Updates Subscription Form. NAVIGATION TIP : For hints on navigating HPE.com to locate the latest drivers, patches, and other support software downloads for ProLiant servers and Options, refer to the Navigation Tips document . SEARCH TIP : For hints on locating similar documents on HPE.com, refer to the Search Tips Document . To search for additional advisories related to iLO, use the following search string: +Advisory +ProLiant -"Software and Drivers" +iLO
Click on a version to see all relevant bugs
Hewlett Packard Enterprise Integration
Learn more about where this data comes from
Bug Scrub Advisor
Streamline upgrades with automated vendor bug scrubs
BugZero Enterprise
Wish you caught this bug sooner? Get proactive today.
