![]() Warning: One very critical caveat is that the use of Tor only applies to TCP connectivity because Tor explicitly does not support UDP, and thus any DNS look-ups performed directly by SpiderFoot’s sfp_dns module will go directly to your configured DNS server. Check the SpiderFoot logs for your scan to see any errors that might be related to Tor. Once you have changed these settings, click the Save Changes button and you are ready to run your scan through Tor. Based on the instrucitons above, this would be 9051. The port Tor is taking control commands on: As explained in the previous section, this is the port you have Tor listening on for control commands, enabling SpiderFoot to instruct it to re-circuit as needed.See the caveat below about DNS in general however. In the case of Tor, all requests going through Tor are resolved through the Tor service, not locally. Pass DNS through the SOCKS Proxy?: This is a SOCKS-specific option which doesn’t apply when using Tor as your proxy.SOCKS Server TCP Port: Whatever port you set in the section above for Tor to use for proxying.This will typically be 127.0.0.1 unless you have configured it differently. SOCKS Server IP Address: Should be the IP Address your Tor server is listening on from the section above.SOCKS Server Type: Simply set the value as ‘TOR’ (without quotes).Scroll down and you will see the following options: To enable Tor in SpiderFoot, go to the Settings menu, and then the Global tab. Unzip the package to a directory of your choice, open the Windows command line and change to the unzipped package “Tor” directory.Ĭheck that it is running and listening on both ports using Task Manager and then netstat should also indicate it is listening on both ports: C:\Tor>netstat /na | findstr 905. ![]() ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |