Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
OpenSSL 'ChangeCipherSpec' MiTM Potential Vulnerability
#7
(12-18-2020, 05:21 PM)kudzu Wrote: Alexandre is the best one to follow up with this as he worked with your project before.

I sent couple of mails re this to him last week and he didnt respond. it is possible forwards to him through this please

(12-18-2020, 07:15 PM)Jose Nilton Pace Wrote: Try to use only these 6 Ciphers, in this exact order:
Code:
ECDHE-RSA-AES256-GCM-SHA384:
ECDHE-RSA-AES128-GCM-SHA256:
DHE-RSA-AES256-GCM-SHA384:
DHE-RSA-AES128-GCM-SHA256:
ECDHE-RSA-AES256-SHA384:
ECDHE-RSA-AES128-SHA256

The last two are weak, according to SSLLABs, but they are needed for SAFARI 6, 7, 8 and Windows Phone 8. If you don't need them, you can remove the last 2 Cipher's.

There is a list of Clients that will not be able to access, image below:

List of Clients that will be able to access using only TLS 1.2 with STRONG CRYPTO

Thank you.
this one also not required please?
!ADH:!EXP:!RC4:!eNULL@STRENGTH
Reply


Messages In This Thread
RE: OpenSSL 'ChangeCipherSpec' MiTM Potential Vulnerability - by pgnair - 12-20-2020, 03:12 AM

Forum Jump:


Users browsing this thread: 1 Guest(s)