Skip to content

Destination Port should be logged #13

@davan77

Description

@davan77

It turns out that the destination port can be important. I can provide examples of several IPs which produce different JARM hash results depending on the port chosen. I believe the following changes would include logging of that port:

510: file.write('{"host":"' + destination_host + '","ip":"' + ip +'","destination_port":"' + str(destination_port) +'","result":"' + result + '"')

512: file.write(destination_host + "," + ip + "," + str(destination_port) + "," + result)

528: sys.stdout.write('{"host":"' + destination_host + '","ip":"' + ip +'","destination_port":"' + str(destination_port) +'","result":"' + result + '"')

532: print("Port: " + str(destination_port))

536: sys.stdout.write('{"host":"' + destination_host + '","ip":null,"result":"' + result + '"')

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions