-
Notifications
You must be signed in to change notification settings - Fork 979
Open
Description
Tor proxy DOES not seem to be supported unless it is undocumented or some trick to get it to work, i can't get it to resolve onion urls, even tried doing --proxy socks://localhost:9050
This occurs with both the kali distribution's release of whatweb and the one from here.
Using proxychains it is able to connect through tor's socks proxy provided you don't pass the --proxy argument, but cannot find onion addresses.
$ ./whatweb --version
WhatWeb version 0.5.5 ( https://morningstarsecurity.com/research/whatweb/ )
$ apt-cache policy whatweb
whatweb:
Installed: 0.5.5-1
Candidate: 0.5.5-1
Version table:
*** 0.5.5-1 500
500 https://http.kali.org/kali kali-rolling/main amd64 Packages
500 https://http.kali.org/kali kali-rolling/main i386 Packages
100 /var/lib/dpkg/status
$ cat /etc/debian_version
kali-rolling
$ ./whatweb -v --proxy localhost:9050 -v -a 1 -c='<some_cookies_were_here>' http://ifconfig.io/
http://ifconfig.io/ [501]
Identifying: http://ifconfig.io/
HTTP-Status: 501
[["Country", [{:string=>"RESERVED", :module=>"ZZ", :certainty=>100}]],
["IP", [{:string=>"172.64.194.16", :certainty=>100}]],
["Title",
[{:name=>"page title",
:string=>"This is a SOCKS Proxy, Not An HTTP Proxy",
:certainty=>100}]]]
WhatWeb report for http://ifconfig.io/
Status : 501 Not Implemented
Title : This is a SOCKS Proxy, Not An HTTP Proxy
IP : 172.64.194.16
Country : RESERVED, ZZ
Summary :
Detected Plugins:
HTTP Headers:
HTTP/1.0 501 Tor is not an HTTP Proxy
Content-Type: text/html; charset=iso-8859-1
Metadata
Metadata
Assignees
Labels
No labels