On 2/26/15, Hongyi Zhao wrote:
> ...
> Could someone please give me some hints on how to let tor use my own dns
> settings instead of using its built-in dns query mechanism?
using your own DNS settings would be a "side channel" and "IP leak/disclosure".
Tor cares about your DNS if configured as
MegaBrutal writes:
> Could someone please help me with this?
>
I think ticket #11211 might be related to what you want. It's still
open. As a start, the wanted behavior should be specified and we
should update the PT spec accordingly.
https://trac.torproject.org/projects/tor/ticket/11211
>
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi
Thanks for running a bridge.
If you want to bind the same pluggable transport protocol to ipv4 and
ipv6 (2 IP:port) I recommend one line for each pluggable transport, as
follows:
ServerTransportPlugin obfs2,obfs3 exec /usr/bin/obfsproxy managed
Could someone please help me with this?
2015-02-19 20:39 GMT+01:00 MegaBrutal :
> Hi,
>
> I want Obfsproxy to listen on both IPv4 and IPv6 interfaces by using
> the following lines in torrc:
>
> ServerTransportPlugin obfs2,obfs3 exec /usr/bin/obfsproxy managed
> ServerTransportListenAddr obfs2 0
>> Just fyi, airport wifis commonly block vanilla ssh, which requires me to do
>> pushes through tor.
> Github has ssh.github.com (IIRC) which accepts SSH on port 443, for exactly
> this problem.
Fair enough, but if anyone asks me then I’ll still tell them how to use ssh
over tor since that a
