Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Issue with Unsafe Legacy Renegotiation Detection in WhatWeb #409

Open
nmasdoufi-ol opened this issue Nov 15, 2024 · 0 comments
Open

Issue with Unsafe Legacy Renegotiation Detection in WhatWeb #409

nmasdoufi-ol opened this issue Nov 15, 2024 · 0 comments

Comments

@nmasdoufi-ol
Copy link

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:

image

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!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant