[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
çå: problem with bridges and a suggestion
- To: <tor-relays@xxxxxxxxxxxxxx>, <tor-relays@xxxxxxxxxxxxx>
- Subject: çå: problem with bridges and a suggestion
- From: wistal <wistal@xxxxxxxxx>
- Date: Wed, 26 May 2010 10:40:25 +0800
- Delivered-to: archiver@xxxxxxxx
- Delivered-to: tor-relays-outgoing@xxxxxxxx
- Delivered-to: tor-relays@xxxxxxxx
- Delivery-date: Tue, 25 May 2010 22:40:34 -0400
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:mime-version :content-class:from:subject:date:importance:x-priority:to :content-transfer-encoding:content-type; bh=K4qh+9h1XE1KuaK/R8AYM2hkvakcexRwgpl+kRZDn4o=; b=LSjUdyMqSAsuGeKbC0DbrdJAEbHKjuRtLOQ4jGTgLhGXdrWeT0tSYsfQ0zYaVpCivr Azh/hsBnvH8cBnFl/eNS+lZVj+O2mtRlu+psPUoomLZBGHVZhby4eNzJufId7tdIV39Z Sy8NiZVastj+QiAzB6RJqYUBlIg/HH4tcscnw=
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:mime-version:content-class:from:subject:date:importance :x-priority:to:content-transfer-encoding:content-type; b=C0+mTAuGq2DjjShbx5yteDGG5LpFPPAydk4MfEhpw9leSnGLrNXdjOYH3Q34jQ8l0h 8bczONKRbAXc723uAkFk8rxkpgQ/ipn0W7gW+gPHC2TtVKLKJIEaUjNhe+CDjp0GGKA2 fyqywHcbMkOCg04GvPArrVDrrn/12+twVVuO8=
- Importance: normal
- Reply-to: tor-relays@xxxxxxxxxxxxxx
- Sender: owner-tor-relays@xxxxxxxxxxxxxx
åïéååïçåäåæåäåï
----- ååéä -----
åää: t f <for.tor.bridge@xxxxxxxxx>
åéæé: 2010å5æ25æ ææä 17:23
æää: tor-relays@xxxxxxxxxxxxx
äé: problem with bridges and a suggestion
dear friends,
problem:
china is blockingÂTORÂ more and more strict,
I can'tÂestablish a TOR circuitÂeven IÂupdated bridges in config file
of torrc with info retrievedÂfrom https://bridges.torproject.orgÂand
email replies from bridges@xxxxxxxxxxxxxxx
this morning,ÂI got some new bridges through a hidden https proxy and
established a TOR circuit, but after some time, I lost the connection
and couldn't establish a TOR circuit any more.
from my knowledge to china's blocking methods, I believe they found my
newly got bridges through network traffic protocol analysis, and
blocked them.
so my suggestion is:
1.
use a general protocol for TOR clients to interact with bridges, so
that they can't distinguish the traffic between TOR clients and
bridges,
so that they can't find new bridges got through private ways.
2.
the general protocol could be https which is encryption protected;
the general protocol could be plain http, if you can encode its
content dynamically and privately, and don't make it display any
fingerprints.
by the way, I'm not a native english speaker, please pardon my awkward english.
sincerely
frank