Skip to content

Issue with Unsafe Legacy Renegotiation Detection in WhatWeb #409

Description

@nmasdoufi-ol

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!

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions