Delivery-Date: Thu, 16 Jul 2015 01:28:42 -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.1 required=5.0 tests=BAYES_00,DKIM_SIGNED,
	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 924CB1E0C95;
	Thu, 16 Jul 2015 01:28:40 -0400 (EDT)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id 7CD7B36DCE;
	Thu, 16 Jul 2015 05:28:35 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id EEFAD36E01
 for <tor-talk@lists.torproject.org>; Thu, 16 Jul 2015 05:28:31 +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 3aMy4D4UWdaw for <tor-talk@lists.torproject.org>;
 Thu, 16 Jul 2015 05:28:31 +0000 (UTC)
Received: from mail-oi0-x234.google.com (mail-oi0-x234.google.com
 [IPv6:2607:f8b0:4003:c06::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 D3FB83662D
 for <tor-talk@lists.torproject.org>; Thu, 16 Jul 2015 05:28:31 +0000 (UTC)
Received: by oihq81 with SMTP id q81so43513271oih.2
 for <tor-talk@lists.torproject.org>; Wed, 15 Jul 2015 22:28:29 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=virgil.gr; s=dkim;
 h=mime-version:from:date:message-id:subject:to:content-type;
 bh=tu36RwKH7rOoc2IXMHPjbaYnFg96/Bw+6XDEE08ypPo=;
 b=PKtDGNg7QqftWEhNAFwN+FRMDoroRCONNKy2Gu+rz+VmhEATw4iZZh7FIIUlfeSGAz
 YPNYKu0U7BkKtDLYnAJLRMlkA5GH7znEftLdn0crUiIS+N2XvJ+Gl45PDR5RmN8B614J
 rlmhG9vmwIEfthUsxEsdf1mtK8iSOkJN42oPw=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=1e100.net; s=20130820;
 h=x-gm-message-state:mime-version:from:date:message-id:subject:to
 :content-type;
 bh=tu36RwKH7rOoc2IXMHPjbaYnFg96/Bw+6XDEE08ypPo=;
 b=fQ2RoMC/uh9Q1nykAXUy+Wpll02WbOzSkWTN5y/FWVMPgsvFdRJZZXwNOGPygeFhhd
 k0kfXZ3lwJC61esfj5t2iYHV0KNZL+sJ6kUXOPUVyleSQepe9Gdf3CQ94IMioo4PKZi+
 QNRz9tkHuLOgaRWGH9rExz9wNDdNgp9Az6cybwOmY8YnLgJbWQ0bPmiJQaDWGvyt0+5p
 25sBM7Fqd3djq+Jngun5tT/IvsxTVIeIbgUTvOL+AjKHYNJ0zto91gHREb3+LgQEpvPK
 ZFX0EnpeXRkypt/atbxDtoKZlS2837xGw37hQtIauAFOB1+q4fBkyeVUsuHdcEMYjdM/
 e3XA==
X-Gm-Message-State: ALoCoQk4kELHy3Fo5D4YGsvuEkdAj93GoTyXnLYrTkhMgdY3oL8C8N0Ry+1Tpgcwd6bei/zG4LHs
X-Received: by 10.202.69.130 with SMTP id s124mr6708517oia.70.1437024508950;
 Wed, 15 Jul 2015 22:28:28 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.202.61.6 with HTTP; Wed, 15 Jul 2015 22:28:09 -0700 (PDT)
From: Virgil Griffith <i@virgil.gr>
Date: Thu, 16 Jul 2015 13:28:09 +0800
Message-ID: <CADop2NGhU-vcLb4AjSk+9-4gZR0gWztFKzoG2-HOPXZV6oYcTA@mail.gmail.com>
To: "tor-talk@lists.torproject.org" <tor-talk@lists.torproject.org>
Subject: [tor-talk] Recommended private key management and recovery
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>

Hello tor-talk!

I have an operations question for those in high-security orgs:
* How do you manage your private keys?
* How do you do recover from a key-compromise?

I ask because there's talk among Singaporean financial tech firms
about migrating to more transparent (yay!) blockchain-based
cryptoledgers, but a sticking point for management is how to reliably
recover from theft of private keys.  I understand there exist
real-world practices like cold-storage as well as cryptographic
practices like requiring quorum of n keys and then regenerating a
stolen key from the quorum.  However, I am seeking something more
concrete for how it all fits together.  And I figured that if any
group of people both competent and transparent enough to discuss this,
it's tor-talk.

I am currently under the impression that this is a largely-solved
problem, but often requires domain-specific knowledge/techniques.
Ergo, I ask.  A paragraph or two overview of the gist would be fine.
Whatever you write I will probably polish into something non-h4x0rs
can understand.

Thanks much,
-Virgil
-- 
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

