Jim and Mike, Thank you for your inputs on this.
The resource: https://mozilla.github.io/server-side-tls/ssl-config-generator/ was very helpful in creating a cipher list that 4D would accept and which got rid of all the insecure options. With regards: I would guess its a syntax issue with 4D. Can you get the current cipher list from 4D and just change one piece at a time until you get rid of the weak portions? Get database parameter(SSL cipher list;$vt_CipherList) returns an empty string till you set it. So you do not seem to be able to get a list of the defaults. Maybe you need to dig into the OpenSSL library (yuck)... Mike also thank you for your list, although it did not make things better. Even with the config -generator whilst the resulting cipher list removed all orange options it did nothing to improve the bars on the already A+ rating. As far as I can tell this is about as good as it gets. I have two outstanding orange text pieces: DNS CAA - No : This appears to be more about who you buy your certificate from and the level of purchase (which is where it can get expensive). Also the message ECDH public server param reuse - Yes : I see no way to affect this. I tried switching off the cache to see if it made a difference but no... If anyone else has any gems I will leave it there happy in the knowledge I have matched the target sites I was trying to match and exceeded many high street baking establishments. Regards, Dougie ________________________________________________________ telekinetix Limited- J. Douglas Cryer Phone : 01234 761759 Mobile : 07973 675 218 2nd Floor Broadway House, 4-6 The Broadway, Bedford MK40 2TE Email : [email protected] Web : http://www.telekinetix.com <http://www.telekinetix.com/> ________________________________________________________ ********************************************************************** 4D Internet Users Group (4D iNUG) FAQ: http://lists.4d.com/faqnug.html Archive: http://lists.4d.com/archives.html Options: https://lists.4d.com/mailman/options/4d_tech Unsub: mailto:[email protected] **********************************************************************

