Nmap tor-consensus-checker NSE Script
This page contains detailed information about how to use the tor-consensus-checker NSE script. For list of all NSE scripts, visit the Nmap NSE Library.
Select: |
---|
Script Overview
Script source code: https://github.com/nmap/nmap/tree/master/scripts/tor-consensus-checker.nse
Script categories: external, safe
Target service / protocol: -
Target network port(s): -
List of CVEs: -
Script Description
The tor-consensus-checker.nse script checks if a target is a known Tor node.
The script works by querying the Tor directory authorities. Initially, the script stores all IPs of Tor nodes in a lookup table to reduce the number of requests and make lookups quicker.
Tor-consensus-checker NSE Script Arguments
This is a full list of arguments supported by the tor-consensus-checker.nse script:
smbdomainThe domain to log in with. If you aren't in a domain environment, then anything will (should?) be accepted by the server.
smbhashA password hash to use when logging in. This is given as a single hex string (32 characters) or a pair of hex strings (both 32 characters, optionally separated by a single character). These hashes are the LanMan or NTLM hash of the user's password, and are stored on disk or in memory. They can be retrieved from memory using the fgdump or pwdump tools.
smbnoguestUse to disable usage of the 'guest' account.
smbpasswordThe password to connect with. Be cautious with this, since some servers will lock accounts if the incorrect password is given. Although it's rare that the Administrator account can be locked out, in the off chance that it can, you could get yourself in trouble. To use a blank password, leave this parameter off altogether.
smbtypeThe type of SMB authentication to use. These are the possible options:
v1
: Sends LMv1 and NTLMv1.LMv1
: Sends LMv1 only.NTLMv1
: Sends NTLMv1 only (default).v2
: Sends LMv2 and NTLMv2.LMv2
: Sends LMv2 only.NTLMv2
: Doesn't exist; the protocol doesn't support NTLMv2 alone. The default,NTLMv1
, is a pretty decent compromise between security and compatibility. If you are paranoid, you might want to usev2
orlmv2
for this. (Actually, if you're paranoid, you should be avoiding this protocol altogether!). If you're using an extremely old system, you might need to set this tov1
orlm
, which are less secure but more compatible. For information, seesmbauth.lua
.
The SMB username to log in with. The forms "DOMAIN\username" and "username@DOMAIN" are not understood. To set a domain, use the smbdomain
argument.
Debug level at which default callbacks will print detailed parsing info. Default: 3
http.host
The value to use in the Host header of all requests unless otherwise set. By default, the Host header uses the output of stdnse.get_hostname()
.
Limit the received body to specific number of bytes. An oversized body results in an error unless script argument http.truncated-ok
or request option truncated_ok
is set to true. The default is 2097152 (2MB). Use value -1 to disable the limit altogether. This argument can be overridden case-by-case with request option max_body_size
.
The maximum memory size (in bytes) of the cache.
http.max-pipeline
If set, it represents the number of outstanding HTTP requests that should be sent together in a single burst. Defaults to http.pipeline
(if set), or to what function get_pipeline_limit
returns.
If set, it represents the number of HTTP requests that'll be sent on one connection. This can be set low to make debugging easier, or it can be set high to test how a server reacts (its chosen max is ignored).
http.truncated-ok
Do not treat oversized body as error. (Use response object flag truncated
to check if the returned body has been truncated.) This argument can be overridden case-by-case with request option truncated_ok
.
The value of the User-Agent header field sent with requests. By default it is "Mozilla/5.0 (compatible; Nmap Scripting Engine; https://nmap.org/book/nse.html)"
. A value of the empty string disables sending the User-Agent header field.
- - -
To use these script arguments, add them to the Nmap command line using the --script-args arg1=value,[arg2=value,..]
syntax. For example:
nmap --script=tor-consensus-checker --script-args smbdomain=value,smbhash=value <target>
Tor-consensus-checker NSE Script Example Usage
Here's an example of how to use the tor-consensus-checker.nse script:
nmap --script=tor-consensus-checker <host>
Tor-consensus-checker NSE Script Example Output
Here's a sample output from the tor-consensus-checker.nse script:
Host script results:
| tor-consensus-checker:
|_ 127.0.0.1 is a Tor node
Tor-consensus-checker NSE Script Example XML Output
There is no sample XML output for this module. However, by providing the -oX <file>
option, Nmap will produce a XML output and save it in the file.xml
file.
Author
- Jiayi Ye
References
- https://nmap.org/nsedoc/scripts/tor-consensus-checker.html
- https://github.com/nmap/nmap/tree/master/scripts/tor-consensus-checker.nse
- https://metrics.torproject.org/collector/recent/relay-descriptors/consensuses/
See Also
Visit Nmap NSE Library for more scripts.
The tor-consensus-checker.nse script may fail with the following error messages. Check for the possible causes by using the code snippets highlighted below found in the script source code. This can often times help in identifying the root cause of the problem.
failed to connect to
Here is a relevant code snippet related to the "failed to connect to " error message:
55: no_cache = true,
56: max_body_size=3*1024*1024
57: })
58:
59: if not response.status then
60: stdnse.print_debug(2, "failed to connect to " .. server.ip)
61: elseif response.status ~= 200 then
62: stdnse.print_debug(2, "%s http error %s", server.ip, response.status)
63: else
64: stdnse.print_debug(2, "consensus retrieved from %s", server.ip)
65: return response.body
%s http error %s
Here is a relevant code snippet related to the "%s http error %s" error message:
57: })
58:
59: if not response.status then
60: stdnse.print_debug(2, "failed to connect to " .. server.ip)
61: elseif response.status ~= 200 then
62: stdnse.print_debug(2, "%s http error %s", server.ip, response.status)
63: else
64: stdnse.print_debug(2, "consensus retrieved from %s", server.ip)
65: return response.body
66: end
67:
failed to connect to directory authorities
Here is a relevant code snippet related to the "failed to connect to directory authorities" error message:
95: if isConnected then
96: break
97: end
98: end
99: if not(isConnected) then
100: stdnse.verbose1("failed to connect to directory authorities")
101: end
102: nmap.registry.tornode.connect = isConnected
103: end
104:
105: function check_tornode_cache(ip)
Version
This page has been created based on Nmap version 7.92.
Go back to menu.