Delivery-Date: Mon, 08 Feb 2016 20:28:49 -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.1 required=5.0 tests=BAYES_00,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 388A31E0CF2;
	Mon,  8 Feb 2016 20:28:48 -0500 (EST)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id 548FA394F8;
	Tue,  9 Feb 2016 01:28:44 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id F3B01394E9
 for <tor-talk@lists.torproject.org>; Tue,  9 Feb 2016 01:28:40 +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 WpcBMLSfhCwz for <tor-talk@lists.torproject.org>;
 Tue,  9 Feb 2016 01:28:40 +0000 (UTC)
Received: from mail-yk0-x234.google.com (mail-yk0-x234.google.com
 [IPv6:2607:f8b0:4002:c07::234])
 (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 D7C08394DE
 for <tor-talk@lists.torproject.org>; Tue,  9 Feb 2016 01:28:37 +0000 (UTC)
Received: by mail-yk0-x234.google.com with SMTP id z7so94657951yka.3
 for <tor-talk@lists.torproject.org>; Mon, 08 Feb 2016 17:28:37 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
 h=content-type:mime-version:subject:from:in-reply-to:date
 :content-transfer-encoding:message-id:references:to;
 bh=rltq0HB0w2Fqy+Kjtn/FKg8B4kZ0LLNTMagJWAtaPag=;
 b=FPUvMIIz8S0Nr4qI9CXVy2oGQr+YIViancN3lkFFS6faIQGNH3zbKJuBCUW6lz7mxc
 IyUdtnWA9Aa6KcL9mZ26dB28E7FZTue22+DbWuwF4PY9kU+TSZyaSDf2CxkFkoOvIrJq
 6Vt6KRlhHXP0//70ZZ9qIt0L6Ddk5BKD9lAXljhIez/3Dg2YINR9j06ds+e6vIB5UNSL
 mCZrkGRqxbeHb+Ipf16mdQGiIQq5KdxpPtWo591t3/Ba6ICx/X9sK6REaMBhUkQPiTJU
 kOjiPDIjv/A8+iw1YkiJ7V+rcI4KvHloGa/0cyaUGwhdZx0ztAjiECYWiQVy/B0X77gr
 P9mA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=1e100.net; s=20130820;
 h=x-gm-message-state:content-type:mime-version:subject:from
 :in-reply-to:date:content-transfer-encoding:message-id:references:to;
 bh=rltq0HB0w2Fqy+Kjtn/FKg8B4kZ0LLNTMagJWAtaPag=;
 b=OSCjXT8/pR9D/ehL6P5azDyPh/kan33BqgzBiTi1WxYa+5q5J8FJLYxaC/lDYI2jNg
 9MeI6ZkzIUuEzuJXY9hwoU7t62WbX3Qq3h1igNt3K7LMVlCQH4gS5Ys13k6xoqh/s8Ph
 79vdfObmyfKk4mQ2csSYavkRlY/qw4zf2WMslaYEpO2frahW+IY1PW73jOskF71ilcPC
 OSpBiAbq1tQYsB5EsEBhRQKsoUDmK7Z+i0PBgZkAEYhnw3MmIuBcns6dlW0FSt6vKpkW
 MeMiZXMlrhWpZHRBtP+E3BqrqPkvISdZ4M+cA05Tu7q96mdSLx4VdDFyukmDpRiZs4NO
 9ENA==
X-Gm-Message-State: AG10YOTwiL6dc6KYQVjjsNwvdQEgaxq8WIbgMaaeMOMw2af2wPjDQPyX/LDe93wXyDRxSQ==
X-Received: by 10.37.101.196 with SMTP id z187mr15620674ybb.17.1454981315561; 
 Mon, 08 Feb 2016 17:28:35 -0800 (PST)
Received: from [172.16.16.122] (50-82-134-187.client.mchsi.com.
 [50.82.134.187])
 by smtp.gmail.com with ESMTPSA id p63sm22986330ywf.8.2016.02.08.17.28.34
 for <tor-talk@lists.torproject.org>
 (version=TLSv1/SSLv3 cipher=OTHER);
 Mon, 08 Feb 2016 17:28:35 -0800 (PST)
Mime-Version: 1.0 (Mac OS X Mail 9.2 \(3112\))
From: Justin <davisjustin002@gmail.com>
In-Reply-To: <1454980907.2669078.515718922.7CAB0F20@webmail.messagingengine.com>
Date: Mon, 8 Feb 2016 19:28:33 -0600
Message-Id: <FF3A8E1C-EB60-4589-B8F5-206E43612CF0@gmail.com>
References: <512753.35066cc4fbb034893b3e6b4367260666f40ff82e@popretr.messagingengine.com>
 <20160208230203.GH9697@happy.bamsoftware.com>
 <1454980907.2669078.515718922.7CAB0F20@webmail.messagingengine.com>
To: tor-talk@lists.torproject.org
X-Mailer: Apple Mail (2.3112)
Subject: Re: [tor-talk] meek-azure was blocked in China for about 4 days
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>

Hi all,
I wonder if the Chinese are going to try and man in the middle Meek to block it?  Does anyone here think that would happen, why or why not?  Also, I wonder what would cause their filtering systems to mess up?
Thanks.

> On Feb 8, 2016, at 7:21 PM, Nathan Freitas <nathan@freitas.net> wrote:
> 
> On Mon, Feb 8, 2016, at 06:02 PM, David Fifield wrote:
>> For about four days (January 29 to February 1, 2016), meek-azure was
>> blocked in China. The blocking may not have been intended for
>> meek-azure, and may not have been deliberate blocking, but it had the
>> effect of blocking the service. It is unblocked again since February 2.
>> 
>> The nature of the event seems to be dropping of HTTPS connections to a
>> specific Azure CDN edge server, cs3.wpc.v0cdn.net, which at the time had
>> an IP address of 68.232.45.200. Plain HTTP connections were not
>> affected. The blocking was not DNS blocking of a specific domain name,
>> nor was it TLS SNI (Server Name Indication) filtering: all domain names
>> we tried for the IP address failed equally.
> 
> Was it port 443 only? What if HTTPS was also made available on port
> 8443? Would that still allow the domain fronting to work?
> 
> -- 
> 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

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

