Delivery-Date: Mon, 02 Nov 2015 22:42:20 -0500
Return-Path: <tor-talk-bounces@lists.torproject.org>
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on moria.seul.org
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_MED,
	T_RP_MATCHES_RCVD autolearn=ham version=3.3.1
X-Original-To: archiver@seul.org
Delivered-To: archiver@seul.org
Received: from eugeni.torproject.org (eugeni.torproject.org [38.229.72.13])
	(using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits))
	(No client certificate requested)
	by khazad-dum.seul.org (Postfix) with ESMTPS id 264711E0DA2
	for <archiver@seul.org>; Mon,  2 Nov 2015 22:42:16 -0500 (EST)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id E7AFE384E7;
	Tue,  3 Nov 2015 03:42:10 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id C588F36251
 for <tor-talk@lists.torproject.org>; Tue,  3 Nov 2015 03:42:06 +0000 (UTC)
X-Virus-Scanned: Debian amavisd-new at 
Received: from eugeni.torproject.org ([127.0.0.1])
 by localhost (eugeni.torproject.org [127.0.0.1]) (amavisd-new, port 10024)
 with ESMTP id SGW7HPvfj7Ai for <tor-talk@lists.torproject.org>;
 Tue,  3 Nov 2015 03:42:06 +0000 (UTC)
Received: from mx1.allurbase.net (mx1.allurbase.net [91.108.68.209])
 by eugeni.torproject.org (Postfix) with ESMTP id 94F173537A
 for <tor-talk@lists.torproject.org>; Tue,  3 Nov 2015 03:42:06 +0000 (UTC)
X-Greylist: delayed 581 seconds by postgrey-1.34 at eugeni;
 Tue, 03 Nov 2015 03:42:06 UTC
Date: Tue, 3 Nov 2015 03:31:15 +0000
From: Cubed <chasintail@emailcontrol.org>
To: tor-talk@lists.torproject.org
Message-ID: <20151103033115.000dd9e8@emailcontrol.org>
In-Reply-To: <CAPjf7ZWQeGzcvEpD_NBVg8kFjDT7GfFuCx6oXp1-RrCex8fdTw@mail.gmail.com>
References: <CAPjf7ZWQeGzcvEpD_NBVg8kFjDT7GfFuCx6oXp1-RrCex8fdTw@mail.gmail.com>
X-Mailer: Claws Mail 3.8.1 (GTK+ 2.24.10; i486-pc-linux-gnu)
Mime-Version: 1.0
Subject: Re: [tor-talk] FTe Bridges
X-BeenThere: tor-talk@lists.torproject.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: tor-talk@lists.torproject.org
List-Id: "all discussion about theory, design,
 and development of Onion Routing" <tor-talk.lists.torproject.org>
List-Unsubscribe: <https://lists.torproject.org/cgi-bin/mailman/options/tor-talk>, 
 <mailto:tor-talk-request@lists.torproject.org?subject=unsubscribe>
List-Archive: <http://lists.torproject.org/pipermail/tor-talk/>
List-Post: <mailto:tor-talk@lists.torproject.org>
List-Help: <mailto:tor-talk-request@lists.torproject.org?subject=help>
List-Subscribe: <https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-talk>, 
 <mailto:tor-talk-request@lists.torproject.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: tor-talk-bounces@lists.torproject.org
Sender: "tor-talk" <tor-talk-bounces@lists.torproject.org>

The bridges.torproject.org site as well as the email service work fine.
Even if the email and/or visit to bridgeDB yielded three bridges, you
only have a single attempt/failure to evaluate as a data point in your
experiment with pluggable transports. Without getting into the protocol
chosen (FTE versus obfs3 versus obfs4 versus scramblesuit, etc), I
would say it's a little early to rule out the countless other variables
in play with your scenario and jump to the conclusion that the bridgeDB
service is down. 

As you'll find, if you choose to try twice, or even a third time,
pluggable transports add an additional layer of complexity to an
already complex machine. Bridges could be down, could be slow, could be
online for a bit only to crumble later and, most importantly, may not
be necessary for your application. 

If your local oppressive government is flagging tor users as suspects
in some heinous plot or your ISP is canceling service to identified tor
users, bridges are a potential solution. If your particular adversary
would be a greater threat by simply knowing you are using tor, bridges
are a possible shield. If you just want to escape the "metadatanet"
that ensnares people, constantly, then simply using tor might be enough
by itself. If you are contributing your computer to the relay network
that powers tor, bridges will never (afaik, I haven't actually looked
into this recently) work for you. 

Beyond the "why" lies the "how". In my experience, and I haven't done
any research in this silo so I may be way off, obfs3 is much more
popular and battle tested than FTE. I can remember FTE as far back as
obfs2, so unless the protocol has been continuously updated, it's
probably not as effective as the newer obfs3 or obfs4. But I have to
emphasize that I haven't looked at FTE for a while and there may be
many things I don't know about it that make it a superior choice for
some users. 

And bringing it back to your initial question; ending with what could
have been the only paragraph sent had I wished to be stingy with the
thought I put into your reply, the bridgeDB website and email service
are both working fine for me and several others. Might I suggest a
light-hearted quick read to give you the push you may find useful in
future endevours, especially those involving tor and it's many exotic
features: A folk-tale I bet you know called "The Little Engine That
Could"  ;)

Three

PS: Apologies, in advance, if I seem sarcastic ~ I simple love
children's stories, oh the memories, such classics!




On Mon, 2 Nov 2015 19:39:07 -0600
Justin Davis <davisjustin002@gmail.com> wrote:

> Hello,
> When I try to use FTE bridges from the bridge db email service, they
> don't work.  Keep in mind I've only tried this once, but has anyone
> else had this issue with FTE or any other pluggable transport bridges
> given out from bridge db?
> Thanks,
> Justin.

-- 
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

