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
Not sure If this helps but we have a DoD client who has relatively strict
security requirements and regular audits. Below is the last cipher settings
they used to pass the security scans.
We've used this tool in the past, but we always have the cert set up on an
Apache proxy in front of our 4D web servers.
https://mozilla.github.io/server-side-tls/ssl-config-generator/
I would guess its a syntax issue with 4D. Can you get the current cipher
list from 4D and just change one piece
3 matches
Mail list logo
