No re-write of DNS2SOCKS required. Just needs to be re-compiled to use port
9150 instead of port 9050:-)
On Thursday, 25 December 2014, Philipp Winter wrote:
> On Wed, Dec 24, 2014 at 11:54:53AM +0000, Richard Brooks wrote:
> > I am a software developer who has been trying to use DNS2
Note if anyone wants to use this utility, that they will need to re-compile
it so that it connects to Socket port 9150 and not 9050, as the 9050 port
is no longer being used by the TOR bundle.
Another issue is that the utility does not look to see if it's dependancies
are running and does not comp
Not a Python man myself, but could come in handy. Thank you.
On Thursday, 25 December 2014, Philipp Winter wrote:
> On Wed, Dec 24, 2014 at 11:54:53AM +0000, Richard Brooks wrote:
> > I am a software developer who has been trying to use DNS2SOCKS but
> haven't
> > h
Just what I'm looking for. Thanks.
On Wednesday, 24 December 2014, grarpamp wrote:
> https://gitweb.torproject.org/torspec.git/tree/
> http://sourceforge.net/projects/dns2socks/files/SourceCode.zip/download
> --
> tor-talk mailing list - tor-talk@lists.torproject.org
> To unsubscribe or change
I am a software developer who has been trying to use DNS2SOCKS but haven't
had much success with it communicating with the latest TOR
Bundle. DNS2SOCKS doesn't seem to have any support to mention, so now am
looking to write an equivalent to DNS2SOCKS myself (possibly also with ip6
support).
As thi
