Good idea. Since I'd be using wget in a virtual machine that does not know the external IP anyway (host-only adapter) - that's what I'd suggest simply to be sure (tor could be running on a separate VM that has access to external internet - bound to that same host-only adapter), I wasn't interested in really finding out, just suggested caution. But yeah, either wireshark or some sniffer, or just wget a file on a server with access to webserver logs ;)
On Wed, Apr 11, 2012 at 4:54 PM, David H. Lipman <dlip...@verizon.net>wrote: > From: "Zebro kojos" <zebro.ko...@gmail.com> > > > I hope wget does not fill in http-proxy headers in its requests, i.e. no >> info is leaking that way? I suppose not. >> >> > When in doubt, load Wireshark for the adapter and sniff your own packets. > Then you will know for sure what goes over the wire. > > > > -- > Dave > Multi-AV Scanning Tool - > http://multi-av.thespykiller.**co.uk<http://multi-av.thespykiller.co.uk> > http://www.pctipp.ch/**downloads/dl/35905.asp<http://www.pctipp.ch/downloads/dl/35905.asp> > > ______________________________**_________________ > tor-talk mailing list > tor-talk@lists.torproject.org > https://lists.torproject.org/**cgi-bin/mailman/listinfo/tor-**talk<https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-talk> > _______________________________________________ tor-talk mailing list tor-talk@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-talk
