Skip to content

cap2hccapx - priority to get correct essid and essid_len #27

Description

@ZerBea

cap2hccapx evaluates the beacon and the proberesponse to get the essid and essid_len. That's not enough:
On hidden ssid's, mailformed packets, and/or packet loss of proberesponse cap2hccapx fails to get the necessary essid.
It's a better way to get essid and essid_len from reassociationrequest or associationrequest which are sent immediately before the eapol sequence.
cap2hccapx should use the following priority (from high to low) te get essid and essid_len:

  1. re-associationrequest
  2. associationrequest
  3. proberesponse
  4. directed proberequest (proberequest to mac_ap - not to BROADCAST)
  5. beacon

Best regards
ZerBea

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions