IETF Logo Mail Archive

Re: [Cfrg] Big-key cryptography

Aaron Zauner <azet@azet.org> Thu, 10 December 2015 22:12 UTC

Return-Path: <azet@azet.org>
X-Original-To: cfrg@ietfa.amsl.com
Delivered-To: cfrg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 710231B2C8C for <cfrg@ietfa.amsl.com>; Thu, 10 Dec 2015 14:12:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 30ACo_lFftnV for <cfrg@ietfa.amsl.com>; Thu, 10 Dec 2015 14:12:09 -0800 (PST)
Received: from mail-lb0-x230.google.com (mail-lb0-x230.google.com [IPv6:2a00:1450:4010:c04::230]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6AEEB1B2C45 for <cfrg@irtf.org>; Thu, 10 Dec 2015 14:12:08 -0800 (PST)
Received: by lbbkw15 with SMTP id kw15so59744232lbb.0 for <cfrg@irtf.org>; Thu, 10 Dec 2015 14:12:06 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=azet.org; s=gmail; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type; bh=SHt8epgEIRiiDYGJ8vhk/EPP/6GHacdeAGf6GJjURPk=; b=QBgjCcMBy09O7ZY1r0sPtmSLsBwbauUp96YN6ASYPQbWyKrB5cpK+0bpusF2X6VLrX M8jV7oJfPHu4TVaQnDOrkn5vilKKIHsQXvBiA+2Vn3tog/dXGXlnBXzbuMJ8EJFFIDF/ yIuNdFyH0j4inYLdMR2dUojcoF3xxUA+c4JII=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:message-id:date:from:user-agent:mime-version:to :cc:subject:references:in-reply-to:content-type; bh=SHt8epgEIRiiDYGJ8vhk/EPP/6GHacdeAGf6GJjURPk=; b=HC4mz/9aWA+9j0WsOw6dTwH8WG2lZJwwRE1KK0o4XicxqQ2uLpjZG5IqVi6MdFmEFl xj9ZWOFZN3vXdQnHEGABK7L139li42OwDyzI1V9vlmr1ZqRH9Qc4E9uLcqSDAZ6CPvHQ 91kSW57Yvp0mKFTOMn1xF4Y46PGGtzikTq+PYeDNvK7DquM5vUnKvQqtA6/p50M+xELU j/2VIjS8nUWds9B5sKS/VMSBI8+pGb9JoU5QJJ6u8hLFnhoWCChPiDA0bmLiu4RHJXw7 z3UOqe8oaynwnn+R6fM1yQK49/TVusA5eRLS9b9SPCb1QkD4lLAw4M8Y2zOTqTGmm75m M4tw==
X-Gm-Message-State: ALoCoQlV2FauVgOjI6DK8Y4OTP47IZuFGoMf1LSTVLLFmpYfVMwI7KPqum9lmkIa7VfWUPxOhYQSC1GmZfZWZw5RfVwj2AryJg==
X-Received: by 10.112.61.166 with SMTP id q6mr6477844lbr.70.1449785526494; Thu, 10 Dec 2015 14:12:06 -0800 (PST)
Received: from [192.168.1.100] ([41.232.114.92]) by smtp.gmail.com with ESMTPSA id 70sm2707218lfw.2.2015.12.10.14.12.04 (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Thu, 10 Dec 2015 14:12:05 -0800 (PST)
Message-ID: <5669F8AF.2000008@azet.org>
Date: Thu, 10 Dec 2015 23:11:59 +0100
From: Aaron Zauner <azet@azet.org>
User-Agent: Postbox 3.0.11 (Macintosh/20140602)
MIME-Version: 1.0
To: Grigory Marshalko <marshalko_gb@tc26.ru>
References: <bcbd3d10ecc43f8bd1e302f095a2ade0@mail.tc26.ru>
In-Reply-To: <bcbd3d10ecc43f8bd1e302f095a2ade0@mail.tc26.ru>
X-Enigmail-Version: 1.2.3
Content-Type: multipart/signed; micalg="pgp-sha512"; protocol="application/pgp-signature"; boundary="------------enigDE47A3AA1274A62DC6EF68E9"
Archived-At: <http://mailarchive.ietf.org/arch/msg/cfrg/LWys5X9QMs3KZE5bdw0yieHhdIY>
Cc: cfrg@irtf.org
Subject: Re: [Cfrg] Big-key cryptography
X-BeenThere: cfrg@irtf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Crypto Forum Research Group <cfrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/cfrg>, <mailto:cfrg-request@irtf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/cfrg/>
List-Post: <mailto:cfrg@irtf.org>
List-Help: <mailto:cfrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/cfrg>, <mailto:cfrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Thu, 10 Dec 2015 22:12:10 -0000


Grigory Marshalko wrote:
> This approach seems to have a lot of drawbacks in real life, since
> secure generation, distribution and storage of keys are usually the main
> problems, and for big keys they could grow exponentially. 
>  

Please re-read the proposal.

Aaron

v2.23.0 | Report a Bug | By Email