Delivery-Date: Wed, 03 Dec 2014 12:53:58 -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.8 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_MED,
	RP_MATCHES_RCVD,URIBL_BLOCKED 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 A511C1E03B6;
	Wed,  3 Dec 2014 12:53:56 -0500 (EST)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id 0C60A31A91;
	Wed,  3 Dec 2014 17:53:52 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id 437DA31A80
 for <tor-talk@lists.torproject.org>; Wed,  3 Dec 2014 17:53:48 +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 n19312monpo3 for <tor-talk@lists.torproject.org>;
 Wed,  3 Dec 2014 17:53:48 +0000 (UTC)
Received: from ruggedinbox.com (ruggedinbox.com [94.156.77.238])
 (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 083E22DCA8
 for <tor-talk@lists.torproject.org>; Wed,  3 Dec 2014 17:53:48 +0000 (UTC)
Mime-Version: 1.0
Date: Wed, 03 Dec 2014 17:53:11 +0000
From: fuckyouhosting@ruggedinbox.com
To: tor-talk@lists.torproject.org
In-Reply-To: <CAM95LegZfCiDnOSB=h9SQ8Ch5gy32n79eVrG9HO_Ju21Ph9tJQ@mail.gmail.com>
References: <CAM95LegZfCiDnOSB=h9SQ8Ch5gy32n79eVrG9HO_Ju21Ph9tJQ@mail.gmail.com>
Message-ID: <9a16ffb19f0dfa622981d6787c3f4697@ruggedinbox.com>
X-Sender: fuckyouhosting@ruggedinbox.com
Subject: Re: [tor-talk] Blockchain.info Tor Hidden Service + Signed
 Certificate
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-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Errors-To: tor-talk-bounces@lists.torproject.org
Sender: "tor-talk" <tor-talk-bounces@lists.torproject.org>

On 2014-12-03 16:17, Nik Cubrilovic wrote:
> Blockchain.info has become the second site after Facebook to roll out
> a Tor hidden service with a CA signed SSL certificate. You can find it
> here:
> 
> https://blockchainbdgpzk.onion/
> 
> My blog post explaining some of the background and implementation
> details is here:
> 
> https://www.nikcub.com/posts/securing-blockchain-users-with-tor-and-ssl/
> 
> Nik

Wow, nice job! Hats off! :)
Just wondering: would the browser, while connecting to 
https://blockchainbdgpzk.onion
and while validating the certificate, 'leak' the request to the CA ?
-- 
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

