Hello,
I happened to see some hidden service name resolution that torsocks was giving
as 127.0.69.0 which I never read about, so I telnetted to it and it's like
another entrance point to Tor, or at least my hidden services(?). I'm a little
confused. Can anyone clarify?
Followup question- is th
22.07.2012, 18:17, "adrelanos" :
> Hansen Jay:
>
>> Can anyone make a layperson explanation of this issue? If I run an
>> application through torsocks, who exactly has to initiate the ipv6
>> traffic to cause the problem? I don't think I have any apps th
22.07.2012, 16:27, "Hansen Jay" :
> 22.07.2012, 15:53, "grarpamp" :
>
>> Torsocks docs are woefully in need of work to match the code. And you may
>> find
>> yourself better off if you ignore the scripts and write your own. All
>> you rea
22.07.2012, 15:53, "grarpamp" :
> Torsocks docs are woefully in need of work to match the code. And you may find
> yourself better off if you ignore the scripts and write your own. All
> you really need is:
>
> LD_PRELOAD=/.../libtorsocks.so TORSOCKS_CONF_FILE=/.../torsocks.conf
> TORSOCKS_DEBUG=
> usewithtor is a script/wrapper and easier to use.
>
> torsocks is the actual binary and has different features (see man torsocks).
No, torsocks also has a wrapper script by the same name. And if the manpage
for torsocks (the wrapper) is correct, it makes usewithtor redundant. I have no
idea
> Please consider updating those pages (wiki can be edited by everyone)
> and submitting trac tickets against the website to fix the mess.
As soon as I figure it out myself! :)
> Torify and tsocks are outdated. Don't bother with it.
OK, but why does Tor deliver torify if that's the case?
>> Ho
