RE: POODLE vs Firmware -- MIDRANGE-L

Subject: RE: POODLE vs Firmware
From: Mike Cunningham <mike.cunningham@xxxxxxx>
Date: Thu, 22 Jan 2015 20:35:00 +0000
List-archive: <http://archive.midrange.com/midrange-l/>
List-help: <mailto:midrange-l-request@midrange.com?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.midrange.com>
List-post: <mailto:midrange-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/options/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=unsubscribe>

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

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

RE: POODLE vs Firmware , rob

This mailing list archive is Copyright 1997-2025 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.