×
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.
Hello Gio,
Am 23.11.2023 um 18:23 schrieb gio.cot via MIDRANGE-L <midrange-l@xxxxxxxxxxxxxxxxxx>:
Last week we migrate from V7R2 to V7R4 .. from since then FTPS go on this
error : Secure connection error, return code -1 ( Help 2° level : “No
encryption type available or specified.”)
This is a recurring topic in this list and most often translates to: "The list of valid encryptions on the local side and on the remote side has no common entries".
Possibile was due to the migration to V7R4 ?
Yes. Newer OS releases (on whatever OS we talk about) usually disable (or actually remove from the code base) weak crypto. If the other side is still on old SSL/TLS library levels, this can lead to your situation.
I suggest you contact the remote side server admin and make sure their machine offers something more current than e. g. 3DES/SHA1. Other mitigations would be your local machine to allow weaker crypto. How this is achieved, I can't tell: I'm not skilled with TLS on IBM i at all.
Probably search the list archives for learning from old posts how to further drill down this issue.
:wq! PoC
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.
midrange.com
