Re: [perpass] stronger crypto requirements
Lucy Lynch <llynch@civil-tongue.net> Thu, 05 September 2013 23:51 UTC
Return-Path: <llynch@civil-tongue.net>
X-Original-To: perpass@ietfa.amsl.com
Delivered-To: perpass@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 257DB11E825D for <perpass@ietfa.amsl.com>; Thu, 5 Sep 2013 16:51:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level:
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MBxfxQg3jSia for <perpass@ietfa.amsl.com>; Thu, 5 Sep 2013 16:51:53 -0700 (PDT)
Received: from hiroshima.bogus.com (hiroshima.bogus.com [IPv6:2001:418:1::80]) by ietfa.amsl.com (Postfix) with ESMTP id 441B711E825C for <perpass@ietf.org>; Thu, 5 Sep 2013 16:51:52 -0700 (PDT)
Received: from hiroshima.bogus.com (localhost [127.0.0.1]) by hiroshima.bogus.com (8.14.3/8.14.3) with ESMTP id r85Npq4J063736 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Thu, 5 Sep 2013 16:51:52 -0700 (PDT) (envelope-from llynch@civil-tongue.net)
Received: from localhost (llynch@localhost) by hiroshima.bogus.com (8.14.3/8.14.3/Submit) with ESMTP id r85NpqLH063733; Thu, 5 Sep 2013 16:51:52 -0700 (PDT) (envelope-from llynch@civil-tongue.net)
Date: Thu, 05 Sep 2013 16:51:52 -0700
From: Lucy Lynch <llynch@civil-tongue.net>
X-X-Sender: llynch@hiroshima.bogus.com
To: Randy Bush <randy@psg.com>
In-Reply-To: <m2txhy3k9t.wl%randy@psg.com>
Message-ID: <alpine.BSF.2.00.1309051651340.47262@hiroshima.bogus.com>
References: <alpine.BSF.2.00.1309051501520.47262@hiroshima.bogus.com> <m2txhy3k9t.wl%randy@psg.com>
User-Agent: Alpine 2.00 (BSF 1167 2008-08-23)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset="US-ASCII"; format="flowed"
Cc: perpass@ietf.org
Subject: Re: [perpass] stronger crypto requirements
X-BeenThere: perpass@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "The perpass list is for discussion of the privacy properties of IETF protocols and concrete ways in which those could be improved. " <perpass.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/perpass>, <mailto:perpass-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/perpass>
List-Post: <mailto:perpass@ietf.org>
List-Help: <mailto:perpass-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/perpass>, <mailto:perpass-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 05 Sep 2013 23:51:54 -0000
missed one - nice critique of the BH talk http://blog.cryptographyengineering.com/2013/08/is-cryptopocalypse-nigh.html - Lucy On Fri, 6 Sep 2013, Randy Bush wrote: >> may be in order: > > so who do we trust to evaluate what is usable today, and who to design > forward? > > randy >
- [perpass] stronger crypto requirements Lucy Lynch
- Re: [perpass] stronger crypto requirements Randy Bush
- Re: [perpass] stronger crypto requirements Lucy Lynch
- Re: [perpass] stronger crypto requirements Stephane Bortzmeyer
- Re: [perpass] stronger crypto requirements Yoav Nir
- Re: [perpass] stronger crypto requirements Yoav Nir