cipher RC4 and SHA1 -- MIDRANGE-L

× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.

Subject: cipher RC4 and SHA1
From: Mike Cunningham <mike.cunningham@xxxxxxx>
Date: Tue, 4 Mar 2014 02:49:19 +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/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=unsubscribe>

We do routine scans of our system and the reports always advise us to turn off RC4 and SHA1 cipher's. It shows it as a low level concern but I still want to try and eliminate this warning on our reports. Is this as simple as just removing these form the QSSLCSL system value? http://pic.dhe.ibm.com/infocenter/iseries/v7r1m0/index.jsp?topic=/rzakz/rzakzqsslcsl.htm

Has anyone found any issues when playing around with the default values as shipped by IBM?

Mike Cunningham

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

RE: cipher RC4 and SHA1 , Peter Connell

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