You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm currently using WhatWeb with a custom plugin for cisco_asa to fingerprint Cisco ASA devices, and I've encountered an error related to unsafe legacy renegotiation when attempting an SSL connection. The error message I receive is:
It seems that unsafe legacy renegotiation is disabled, but I'm unsure whether WhatWeb has support for detecting this issue or handling it correctly. I wanted to ask if there's any built-in support for detecting unsafe legacy renegotiation, and whether there's any way to configure WhatWeb to bypass this issue or provide more detailed information on the SSL/TLS renegotiation status.
Any guidance or pointers on how to handle this would be appreciated.
Thank you!
The text was updated successfully, but these errors were encountered:
Hello,
I'm currently using WhatWeb with a custom plugin for
cisco_asa
to fingerprint Cisco ASA devices, and I've encountered an error related to unsafe legacy renegotiation when attempting an SSL connection. The error message I receive is:It seems that unsafe legacy renegotiation is disabled, but I'm unsure whether WhatWeb has support for detecting this issue or handling it correctly. I wanted to ask if there's any built-in support for detecting unsafe legacy renegotiation, and whether there's any way to configure WhatWeb to bypass this issue or provide more detailed information on the SSL/TLS renegotiation status.
Any guidance or pointers on how to handle this would be appreciated.
Thank you!
The text was updated successfully, but these errors were encountered: