The wonderful security updates in Firefox (and Chrome) will give you the dreaded SSL_ERROR_BAD_MAC_ALERT. So no more ILO for you
How to mitigate that?, well first do as told in the article above, go to about:config in firefox and set the security.tls.version.fallback-limit to 1.
How you can access the ILO and update the firmware to 2.29 for ILO2 (or higher), as instructed here, you can fetch the ILO2 firmware Here
HP has a habit of only updating the Windoze firmware binaries, forgetting that most of the internet runs on Linux, but anyway just download the EXE and extract the ilo229.bin from the file.
If you don’t like the clickerdyclick web interface, or have more than 2 servers to update, it makes sense to put your binary on some web server in your environment and just ssh into your ILO and update from there, the magic is done like so:
load -source http://192.168.1.11/iso/HP/Firmware/ilo2_229.bin /map1/firmware1
(192.168.1.11/iso…. is our internal web server of course, replace with your own)
O and don’t forget to set your FireFox security.tls.version.fallback-limit back to 3
How to mitigate that?, well first do as told in the article above, go to about:config in firefox and set the security.tls.version.fallback-limit to 1.
How you can access the ILO and update the firmware to 2.29 for ILO2 (or higher), as instructed here, you can fetch the ILO2 firmware Here
HP has a habit of only updating the Windoze firmware binaries, forgetting that most of the internet runs on Linux, but anyway just download the EXE and extract the ilo229.bin from the file.
If you don’t like the clickerdyclick web interface, or have more than 2 servers to update, it makes sense to put your binary on some web server in your environment and just ssh into your ILO and update from there, the magic is done like so:
load -source http://192.168.1.11/iso/HP/Firmware/ilo2_229.bin /map1/firmware1
(192.168.1.11/iso…. is our internal web server of course, replace with your own)
O and don’t forget to set your FireFox security.tls.version.fallback-limit back to 3
No comments:
Post a Comment