Client Use with Newly Updated ASNMap API Auth

[BytesInFlight]

Interactsh version:

[INF] Current Version: 1.2.0

Current Behavior:

ASN lookups using the ASNMAP-API aren't being made. This has been tested by configuring the API key through environment variable and by using the -auth flag parameter on ASNMAP. ASNMAP runs successfully on its own independent of Interactsh. The following warning is present in the verbose run output.

[asnmap-api] missing or invalid api key (get free api & configure it from https://cloud.projectdiscovery.io/?ref=api_key)

Expected Behavior:

JSON output showing a successful ASN lookup:

{"protocol":"http","unique-id":"xxx","full-id":"xxx","raw-request":"GET / HTTP/1.1\r\nHost: xxx.oast.me\r\nAccept: */*\r\nUser-Agent: curl/7.81.0\r\n\r\n","raw-response":"HTTP/1.1 200 OK\r\nConnection: close\r\nContent-Type: text/html; charset=utf-8\r\nServer: oast.me\r\nX-Interactsh-Version: 1.0.7\r\n\r\n\u003chtml\u003e\u003chead\u003e\u003c/head\u003e\u003cbody\u003e84wb1ttcnycp7gg9a33sv82t33g448rec\u003c/body\u003e\u003c/html\u003e","remote-address":"xxx.xxx.xxx.xxx","timestamp":"2023-01-05T07:54:04.72192316Z","asninfo":[{"asn":"ASxxxx","country":"xx","first-ip":"xxx.xxx.xxx.0","last-ip":"xxx.xxx.xxx.255","org":"ASN-xxxx"}]}

Steps To Reproduce:

1. Run 'interactsh ...' with the following commandline as an example: sudo ./interactsh-client -s example.dev -asn -v
2. Perform test by executing the following curl: curl cqgm1kovkgtnthp1cpsgtftmc6q9463g6.example.dev
3. The following error shows up in the verbose output in place of ASN data: [asnmap-api] missing or invalid api key (get free api & configure it from https://cloud.projectdiscovery.io/?ref=api_key)

Anything else:

• Issue being submitted at the request of the PD Team. Learned via outreach on July 24, 2024 at 3:26pm in the Project Discovery community Discord server channel #interactsh that "the auth part of api was recently introduced, so looks like env support in client needs to be added"