f number, lenghts and times of
packets make it possible to establish the fact of connection. Even user
had been loading several pages from different sites simultaneously, its
possible to evolve packets by its lengths because each TOR node in
chain decrease lenght of packet by fixed number of bytes
ode selection for rule weight
as guard
many times.
obfs3, obfs2 and bridges without pluggable transport all are working
correctly.
WBR, Alan Hiew
--
tor-talk mailing list - tor-talk@lists.torproject.org
To unsubscribe or change other settings go to
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-talk
doesn't make Tor connection.
Process has stopped at "Establishing an encrypted directory connection".
Tails 1.3 and later have to support bfs4 bridges as announced.
Why this can happen?
WBR, Alan Hiew
--
tor-talk mailing list - tor-talk@lists.torproject.org
To unsubscribe or change ot
m them.
Reason to do it... may be possible attacks on site from Tor hacking
users or some other network abuse.
For example, Wikipedia partially block Tor users and they can read it
but can't login and edit pages. ripe.net blocking whois service from
many Tor exits. Can we think that all
Hello, listers!
I have detected that some IP addres of obfs3 briges have demasking
WHOIS information.
For example
obfs3 bridge with IP at range 192.36.31.0 - 192.36.31.255
(there are several bridges; I dont want to publish it at the list but
can send by private messages if somebody wants).
RI
