RE: Possible issue with PTF SI55522 -- MIDRANGE-L

Good News Everybody!

The new search engine is LIVE!

Please report any problems to david (at) midrange.com.

Subject: RE: Possible issue with PTF SI55522
From: rob@xxxxxxxxx
Date: Mon, 5 Jan 2015 09:00:23 -0500
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>

This isn't one of those "if it ain't broke, don't fix it" issues. You'd
better read this:
https://www.ibm.com/developerworks/community/wikis/home?lang=en#!/wiki/W1c12c273752d_4cb8_b000_8375ec43426d/page/OpenSSL%20PCI%20Compliance

If you don't care about PCI compliance, and you don't care about being
open to a denial of service attack then just ignore these PTFs.

I'm not poo-poo ing the vendor's concerns. What I am saying is that just
ignoring the PTF's is not a good plan either.

Rob Berendt

As an Amazon Associate we earn from qualifying purchases.

This mailing list archive is Copyright 1997-2026 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.