× 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.



A simple way is to specify SSLProtocolDisable SSLv2 SSLv3 TLSV1 in your
httpd.conf and restart your http server. It only affects that single http
server, does not affect other http servers and other applications.

http://www-01.ibm.com/support/knowledgecenter/#!/ssw_ibm_i_72/rzaie/rzaiemod_ibm_ssl.htm%23sslprotocoldisable

2016-01-13 22:14 GMT+08:00 Mike Cunningham <mike.cunningham@xxxxxxx>:

I need to disable protocol TLS 1.0 on just our public facing HTTP server
running on our IBM i server. We still need to allow TLS 1.0 for telnet (for
now). I looked in DCM and can see the option to not use *PGM definition for
protocols and I can select just TLS 1.2 and 1.1. Before I click "Apply" on
this change I just wanted to see if this is all that needs changed or if I
also need to change the cipher specs or SSL signatures. Any confirmation
from anyone else who has had to make this change would be appreciated.

Thanks

Mike Cunningham
VP of Information Technology Services/CIO
Pennsylvania College of Technology


--
This is the Web Enabling the IBM i (AS/400 and iSeries) (WEB400) mailing
list
To post a message email: WEB400@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/web400
or email: WEB400-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/web400.



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.