Delivery-Date: Mon, 08 Feb 2016 20:22:01 -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,UNPARSEABLE_RELAY 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 2950D1E0CF2;
	Mon,  8 Feb 2016 20:21:59 -0500 (EST)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id 5B9E0394E7;
	Tue,  9 Feb 2016 01:21:54 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id 3EBF3393A2
 for <tor-talk@lists.torproject.org>; Tue,  9 Feb 2016 01:21:51 +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 j08M_CRPFQ0n for <tor-talk@lists.torproject.org>;
 Tue,  9 Feb 2016 01:21:51 +0000 (UTC)
Received: from paulo.mayfirst.org (paulo.mayfirst.org [209.234.253.240])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by eugeni.torproject.org (Postfix) with ESMTPS id 2A29C3939F
 for <tor-talk@lists.torproject.org>; Tue,  9 Feb 2016 01:21:51 +0000 (UTC)
Received: from paulo.mayfirst.org (unknown [127.0.0.1])
 by paulo.mayfirst.org (Postfix) with ESMTP id 8CA693F32
 for <tor-talk@lists.torproject.org>; Mon,  8 Feb 2016 20:21:48 -0500 (EST)
Received: from [127.0.0.1] (localhost [127.0.0.1]) (Authenticated sender:
 nathanfreitas@paulo.mayfirst.org) with ESMTPSA id 7A8AD3F2F
Received: from compute5.internal (compute5.nyi.internal [10.202.2.45])
 by mailauth.nyi.internal (Postfix) with ESMTP id 174D920947
 for <tor-talk@lists.torproject.org>; Mon,  8 Feb 2016 20:21:48 -0500 (EST)
Received: from web1 ([10.202.2.211])
 by compute5.internal (MEProxy); Mon, 08 Feb 2016 20:21:48 -0500
Received: by web1.nyi.internal (Postfix, from userid 99)
 id E7022AE5A6B; Mon,  8 Feb 2016 20:21:47 -0500 (EST)
Message-Id: <1454980907.2669078.515718922.7CAB0F20@webmail.messagingengine.com>
X-Sasl-Enc: zWqOZS068iz+b/QrOfSvg1+gEtLc8kyvhQxta2dLDK7n 1454980907
From: Nathan Freitas <nathan@freitas.net>
To: tor-talk@lists.torproject.org
MIME-Version: 1.0
X-Mailer: MessagingEngine.com Webmail Interface - ajax-57359b3d
In-Reply-To: <512753.35066cc4fbb034893b3e6b4367260666f40ff82e@popretr.messagingengine.com>
References: <512753.35066cc4fbb034893b3e6b4367260666f40ff82e@popretr.messagingengine.com>
 <20160208230203.GH9697@happy.bamsoftware.com>
Date: Mon, 08 Feb 2016 20:21:47 -0500
X-Virus-Scanned: ClamAV using ClamSMTP
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>

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

