We have the above version of FTP2 we are reducing the ciphers on our Secure server to address the logjam issue. When testing we fail. We have reduced to two ciphers, TLS_RSA_WITH_AES_128_CBC_SHA256 and TLS_RSA_WITH_AES_256_CBC_SHA265
Here is the last of the log
--Connect_Ftp2 --ChilkatLog 220-DMV Secure File Transfer
220- 220- 220 Secure FTP Server ready. AUTH TLS 234 SSLv23/TLSv1 ChilkatLog: ChangeRemoteDir:
asked Aug 10 '15 at 17:09
Thanks, I was working on reducing ciphers for PCI compliance, thru hunt and peck I was able to find an allowable combination.
answered Aug 14 '15 at 18:14
Not sure about 188.8.131.52, but the current documentation mentions that as of 184.108.40.206 the following about supported ciphers. Dees it help?
SslAllowedCiphers As String
Introduced in version 220.127.116.11
Provides a means for setting a list of ciphers that are allowed for SSL/TLS connections. The default (empty string) indicates that all implemented ciphers are possible: aes256-cbc, aes128-cbc, 3des-cbc, and rc4. To restrict SSL/TLS connections to one or more specific ciphers, set this property to a comma-separated list of ciphers such as "aes256-cbc, aes128-cbc". The order should be in terms of preference, with the preferred algorithms listed first. The server however, chooses from among the algorithms listed.
Starting in v18.104.22.168, Chilkat will by-default disallow all possible usage of RSA keys that are less than 1024 bits. To allow for 512 bits or above, add "rsa512" to the list of algorithms in the SslAllowedCiphers list. To allow only 2048 bits or above, add "rsa2048" to the list of algorithms. (Adding "rsa1024" chooses the same as the default.)
answered Aug 14 '15 at 08:33