Delivery-Date: Sat, 21 Nov 2015 16:56:25 -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=-3.1 required=5.0 tests=BAYES_00,BODY_URI_ONLY,
	DKIM_ADSP_CUSTOM_MED,DKIM_SIGNED,FREEMAIL_FROM,RCVD_IN_DNSWL_MED,
	T_DKIM_INVALID,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 343141E0AEA;
	Sat, 21 Nov 2015 16:56:24 -0500 (EST)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id 5637D37C81;
	Sat, 21 Nov 2015 21:56:19 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id 53F47370AF
 for <tor-talk@lists.torproject.org>; Sat, 21 Nov 2015 21:56:15 +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 JL0cL9ihtyE9 for <tor-talk@lists.torproject.org>;
 Sat, 21 Nov 2015 21:56:15 +0000 (UTC)
Received: from mail-yk0-x229.google.com (mail-yk0-x229.google.com
 [IPv6:2607:f8b0:4002:c07::229])
 (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits))
 (Client CN "smtp.gmail.com",
 Issuer "Google Internet Authority G2" (not verified))
 by eugeni.torproject.org (Postfix) with ESMTPS id 220093700F
 for <tor-talk@lists.torproject.org>; Sat, 21 Nov 2015 21:56:15 +0000 (UTC)
Received: by ykba77 with SMTP id a77so201925132ykb.2
 for <tor-talk@lists.torproject.org>; Sat, 21 Nov 2015 13:56:12 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
 h=mime-version:in-reply-to:references:date:message-id:subject:from:to
 :content-type; bh=4garum7DW7QvxcYzZ6t7p7OgtK2MXyKqDugHvrULH2Q=;
 b=GZHaKubwwO+2benrUe9s8Tz+2shFy37Ky55inlrti3xzD7MtkLTBf8k0o4myJx1W+C
 u+QD4c4LrJt/Ol6OFh/Ax0RR3hxQ1yBZ2CrJchaoprfUUc3lJKJ8GONMIv9b6M+6ipyH
 SsHc4VVkRdsyTekNuBMYJVlqJNgqwHMbYDkH7fo5hbevMBrzjcfpbtusW1xm5cQRiWYX
 0XbKuOaYJP56RPnvdrVv0nNFHPiXnP7OZtHWwcyU29XMzxFXKLSROmkp6F7aqrm00okA
 D5cUBN+1ErpCYeRjYyHg7rt1iXb5q6MMt6o1BfGj/drHN8irsegdAVpGf1tUN86vdJWY
 Bn7A==
MIME-Version: 1.0
X-Received: by 10.129.110.198 with SMTP id j189mr5532111ywc.11.1448142972742; 
 Sat, 21 Nov 2015 13:56:12 -0800 (PST)
Received: by 10.129.74.4 with HTTP; Sat, 21 Nov 2015 13:56:12 -0800 (PST)
In-Reply-To: <20151121214350.GF16523@inner.h.apk.li>
References: <CAPjf7ZXsPCo2U0rXD2uXWsrxc5Do=9_1KUyY1JrU+gYztNdXbg@mail.gmail.com>
 <564F9FD7.3060803@riseup.net>
 <AA7E7174-841B-4710-BFFA-0CE406F9F22F@gmail.com>
 <564FA467.3060905@riseup.net>
 <CAB7TAMmfAUO1+_kFhMXvSKGZCaBp-ZuMQ8BzHYt_GqphojEofA@mail.gmail.com>
 <8AAB7E6C-291F-41B8-B8DC-C0D4CB2F37B9@gmail.com>
 <20151121214350.GF16523@inner.h.apk.li>
Date: Sat, 21 Nov 2015 16:56:12 -0500
Message-ID: <CAB7TAMn2R01A7po+bpZX34RDgWZ4CMv2PqZi7vvDaj4fMRz0ww@mail.gmail.com>
From: Allen <allenpmd@gmail.com>
To: tor-talk@lists.torproject.org
X-Content-Filtered-By: Mailman/MimeDel 2.1.15
Subject: Re: [tor-talk] MITM attack on TLS
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>

>
> > SSH is probably more dangerous than OBFS4 because it coulee be detected
> with a DPI fingerprint.  They might question that.  I think Tor with
> transports is good.
>
> On that paranioa level OBFS4 is as dangerous as SSH - it doesn't matter
> if they see traffic they can fingerprint as ssh or they see traffic they
> cannot fingerprint. They get suspicious in both cases.
>
>
Personally, I would think SSH is much safer.  It is used by IT people all
the time for server management, so they will understand it.  The
destination address will be a cloud server, which you can simply say you
are using for a personal project.  OBFS4 on the other hand is not normally
used by IT people--it is used to get around IT people.  They will
immediately be very suspicious if they are able to figure out the
protocol.  And the destination IP address is who-knows-what, which could by
itself raise questions and might even lead them to think a computer on
their network could be infected with a virus that needs immediate
investigation.  In the end, a protocol they know and understand and use in
their own work will be much less threatening to them than something they
don't.
-- 
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

