[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
problem with bridges and a suggestion
- To: or-talk@xxxxxxxxxxxxx
- Subject: problem with bridges and a suggestion
- From: t f <for.tor.bridge@xxxxxxxxx>
- Date: Tue, 25 May 2010 17:18:44 +0800
- Delivered-to: archiver@xxxxxxxx
- Delivered-to: or-talk-outgoing@xxxxxxxx
- Delivered-to: or-talk@xxxxxxxx
- Delivery-date: Tue, 25 May 2010 05:18:50 -0400
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:date:message-id :subject:from:to:content-type:content-transfer-encoding; bh=Kfach+wYocgQgdefPtKvBeeZo9FMPOLjaU2T89JDUNU=; b=u18Ly5xcg1mjA2IWQqf+vOtlvSpNb+yMcYQuRtTOXwcLuVjUUGBE9NORriGL08Iqbj QxHTEQpUQaOxtTnV1hdAUvwcVFhrnaT1cv32YbHL5GRwL4FWPP4bxnPHgWvYlhxJsGMd T0Jwgr5ELVfjKlIUoxcMA9bEWzYpjhJktfrTQ=
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type :content-transfer-encoding; b=COOxCkZl8kqlUJA0KyZej0yMRRLBo5mfcsZftUlCDROImlmKUrf38XqICF62Q/CEr7 y+tOPgqjwTT01tQv4V81WkYRdtEq6aHFs197I2nH93TXuVG1Gj2tiObIHF4jkPJG6442 3DzOzqTJIO/5AoJW/KTsuI1JPluz4+x0DRPZU=
- Reply-to: or-talk@xxxxxxxxxxxxx
- Sender: owner-or-talk@xxxxxxxxxxxxx
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
***********************************************************************
To unsubscribe, send an e-mail to majordomo@xxxxxxxxxxxxxx with
unsubscribe or-talk in the body. http://archives.seul.org/or/talk/