Delivery-Date: Thu, 02 Oct 2014 10:08:04 -0400
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.9 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_MED,
	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 AE3891E087D;
	Thu,  2 Oct 2014 10:08:02 -0400 (EDT)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id 8F32E2D5C3;
	Thu,  2 Oct 2014 14:07:57 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id 748C12CFC5
 for <tor-talk@lists.torproject.org>; Thu,  2 Oct 2014 14:07:53 +0000 (UTC)
X-Virus-Scanned: Debian amavisd-new at eugeni.torproject.org
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 PmJFv4C3pG9z for <tor-talk@lists.torproject.org>;
 Thu,  2 Oct 2014 14:07:53 +0000 (UTC)
Received: from atl4mhob14.myregisteredsite.com
 (atl4mhob14.myregisteredsite.com [209.17.115.52])
 by eugeni.torproject.org (Postfix) with ESMTP id 470522CF7D
 for <tor-talk@lists.torproject.org>; Thu,  2 Oct 2014 14:07:53 +0000 (UTC)
Received: from mailpod.hostingplatform.com ([10.30.71.210])
 by atl4mhob14.myregisteredsite.com (8.14.4/8.14.4) with ESMTP id
 s92E7nIS005321
 for <tor-talk@lists.torproject.org>; Thu, 2 Oct 2014 10:07:49 -0400
Received: (qmail 11481 invoked by uid 0); 2 Oct 2014 14:07:49 -0000
X-TCPREMOTEIP: 162.17.205.153
X-Authenticated-UID: datzrott@alizeepathology.com
Received: from unknown (HELO ALPATH26)
 (datzrott@alizeepathology.com@162.17.205.153)
 by 0 with ESMTPA; 2 Oct 2014 14:07:49 -0000
From: "Derric Atzrott" <datzrott@alizeepathology.com>
To: <tor-talk@lists.torproject.org>
References: <006e01cfdd7f$9fa4b370$deee1a50$@alizeepathology.com>
 <542C2D15.2020101@riseup.net>
 <012401cfdda3$01978a30$04c69e90$@alizeepathology.com>
 <012601cfdda7$67c319b0$37494d10$@alizeepathology.com>
 <CAJoS0DX-7XCY4E=DGuUuptwJFmB_VG1eVJv3pDJ-z5tNvBAMaA@mail.gmail.com>
 <013201cfddb1$020a19c0$061e4d40$@alizeepathology.com>
 <1412194370.28612.6.camel@anglachel>
 <014401cfddb6$f00ca2a0$d025e7e0$@alizeepathology.com>
 <1412199173.28612.8.camel@anglachel>
 <007f01cfde3f$ab386720$01a93560$@alizeepathology.com>
 <542D5854.7080902@riseup.net>
In-Reply-To: <542D5854.7080902@riseup.net>
Date: Thu, 2 Oct 2014 10:07:49 -0400
Organization: Alizee Pathology LLC.
Message-ID: <00ae01cfde4a$3f99bd60$becd3820$@alizeepathology.com>
MIME-Version: 1.0
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQH3Ic0CFjPy8W89qtGxwDKfI6rplgJnxOh9AkYCeUgBHWuqqgGv6kARAlF7UC8BjUQXlgD0SwWPA4dhLroBk50SSAHi18qemzPv+XA=
Content-Language: en-gb
Subject: Re: [tor-talk] Wikimedia and Tor
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>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

>> I liked the GPG idea, and brought it back to Wikitech-l. I'll let
>> you guys know if anyone there finds a way to completely break it.
> 
> There's another possibility that's probably easier to implement and
> test, but isn't so broadly useful as a hard-to-generate GnuPG key. In
> creating a hidden service, the Tor client generates an RSA private_key
> and uses the first 80 bytes of the key's SHA1 hash as the hostname.
> Vanity hostnames being popular, there are published methods.[0]

I'm not entirely sure what you are suggesting?  Are you suggesting
we leverage specify some portion of a SHA1 hash and require that
the Tor clients trying to edit Wikipedia create a hidden service key
that ends up matching that?

Or are you suggesting that we do something involving requiring editors
using Tor to create a hidden service with a certain hostname (are those
hostnames called descriptors, I think they are, but I'm not 100% sure)?

Or something else entirely.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (MingW32)

iD8DBQFULVwtRHoDdZBwKDgRAgq9AJ9Nn18aeRxWkGe9m91AOmB86FAkJQCfZauN
d93BMkJBRc4tTijQFsgXdi8=
=5XZP
-----END PGP SIGNATURE-----

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

