Aaahhh - Didn't catch the reference to HMC before. We don't have an HMC to deal with (at least not yet) so not worried about that. I need to stop SSLv2 and v3 over HTTPS and secure telnet.
-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of rob@xxxxxxxxx
Sent: Thursday, January 22, 2015 4:20 PM
To: Midrange Systems Technical Discussion
Subject: RE: POODLE vs Firmware
and I wholeheartedly agree with them. And that is what I am saying.
Let me repeat. They will stop communicating between the HMC and the firmware using SSLvWhatever. To do that they will need to use TLS or whatever. To use TLS or whatever they will need to modify the code for firmware and HMC.
Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1 Group Dekko Dept 1600 Mail to: 2505 Dekko Drive
Garrett, IN 46738
Ship to: Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com
From: Mike Cunningham <mike.cunningham@xxxxxxx>
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Date: 01/22/2015 03:35 PM
Subject: RE: POODLE vs Firmware
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx>
Our external scan service that we use for PCI testing does not mention the
possibility of a patch to fix the failed status. They just say the only
option is to disable it.
-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of
rob@xxxxxxxxx
Sent: Thursday, January 22, 2015 3:23 PM
To: Midrange Systems Technical Discussion
Subject: RE: POODLE vs Firmware
If you turn off SSLv2 and SSLv3 you have to communicate via alternative
methods.
Methinks this is the point of these 'patches' to firmware and HMC code.
Rob Berendt
midrange.com
