Re: [Curdle] comments on draft-ietf-curdle-rsa-sha2-03.txt
denis bider <denisbider.ietf@gmail.com> Sat, 08 April 2017 11:20 UTC
Return-Path: <denisbider.ietf@gmail.com>
X-Original-To: curdle@ietfa.amsl.com
Delivered-To: curdle@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C25061287A3 for <curdle@ietfa.amsl.com>; Sat, 8 Apr 2017 04:20:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.099
X-Spam-Level:
X-Spam-Status: No, score=-0.099 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 n8YAz4mmxp5x for <curdle@ietfa.amsl.com>; Sat, 8 Apr 2017 04:20:51 -0700 (PDT)
Received: from mail-qt0-x22b.google.com (mail-qt0-x22b.google.com [IPv6:2607:f8b0:400d:c0d::22b]) (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 680C6120725 for <curdle@ietf.org>; Sat, 8 Apr 2017 04:20:51 -0700 (PDT)
Received: by mail-qt0-x22b.google.com with SMTP id c45so35960931qtb.1 for <curdle@ietf.org>; Sat, 08 Apr 2017 04:20:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=eYmqjCGKJgBGI5FGgj5dPiVW8e0FyoDhDjTwOYQy2mk=; b=Xqa470LgoeLcEZyl1bjnLkmT2/W/PmMCqDLytkdBB2E/K5yb6FQ+WDEFB+bgzlOojJ 1Z7Y/18VbD1/kTmNzBvMXJI7yCkGz5/Gi9Salp7NQhYb/LsZU6EXJB7sgrp/hkxDLHU0 b8hNdSvQA6L2A4jAUSI2WXnC3zfIfgMI0KDrpcLFyHNYEjH7uX687NFoZCRLgxIK9QmL eZ9nNXA1pgkMze6SvDZcg+d7UAlrpLquJTillgTP4aqRtv6oe1Myi6RsvHGtnjfrLZFu EvwjHU1UIW4TegQ9fPLkLHfrfoXpbrX27fFHoOpkMOLJu8ODCMbAhygzSBBf5b14DLHl xTjA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=eYmqjCGKJgBGI5FGgj5dPiVW8e0FyoDhDjTwOYQy2mk=; b=MdRjJgamUy7b8VLnD6Ws3ESyueUYRTn5rGanAWlsluWMfpUEIgmt4Q7M0uL6xcQmqJ vN58rhXS8hs1A6D4gNXhSkX/j4A0XKieE58DqwlatTUKtzLq/vATOhFiAVFgQiNs5gH4 Ex/9+3TIrq6qef+cJIfeMLheyZtsvzU5tYl0yOBxXTyriOS3GUQkhu/qFY4QdbDP4yVU IW5I2iZm22ZsQOtUM8jKQwSpO3bSFLbgYHGO6BG20h9PSytRW1BQk3bJIGhIkbi64gYc h7S4l/7Yq3lzY3fE/vqYTd1wtY/hKDikFpQs2w6m6DIsWXSyfAC9zaDlos1OFPTV7j/G ZedA==
X-Gm-Message-State: AFeK/H1+ocalwXtuWOfVdutVvC7UGBa0KiKVIDYlpyP8pae1SIJILza/nufUZu9znCREPLqF8513AOw8Joyj8A==
X-Received: by 10.237.59.248 with SMTP id s53mr18403822qte.177.1491650450391; Sat, 08 Apr 2017 04:20:50 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.12.138.239 with HTTP; Sat, 8 Apr 2017 04:20:49 -0700 (PDT)
In-Reply-To: <1491622956832.39612@cs.auckland.ac.nz>
References: <CADPMZDByTiWov0vp2Tk1n9dnnkfwepO+UsAnh3rdsrbem2H=VQ@mail.gmail.com> <1490575901696.39454@cs.auckland.ac.nz> <CADPMZDDNZTznKBJ2-vf4MJFjP0Bx34ALF8JCVBhwv12Pdm=XcA@mail.gmail.com> <CADZyTk=L2mKheNkHQ+jtecspLnR2rGc1BajkTKQ0G3cynxkwow@mail.gmail.com> <20170327072447.GA2827@LK-Perkele-V2.elisa-laajakaista.fi> <CADPMZDAmuUKy_AJ9aYd4YYAmO5ZU-8z0P7EZwq2aG+jJM-kRaQ@mail.gmail.com> <CADZyTk=r9quAZxvyQgLd7PrvvhzoQ96s5CPqHcFNaGez8igYcw@mail.gmail.com> <CACsn0c=62mYoYm5MMBK5WKXQjffFBrHDd1EgOZ7vo-JkDgg+Dw@mail.gmail.com> <1491622956832.39612@cs.auckland.ac.nz>
From: denis bider <denisbider.ietf@gmail.com>
Date: Sat, 08 Apr 2017 05:20:49 -0600
Message-ID: <CADPMZDDQN0Bu7JfoMhfh+LsKpMxnLEqdOGP9Z+ucQWxdnMARJA@mail.gmail.com>
To: Peter Gutmann <pgut001@cs.auckland.ac.nz>
Cc: Watson Ladd <watsonbladd@gmail.com>, Daniel Migault <daniel.migault@ericsson.com>, "curdle@ietf.org" <curdle@ietf.org>, Ilari Liusvaara <ilariliusvaara@welho.com>
Content-Type: multipart/alternative; boundary="94eb2c1914ac3987de054ca5efa1"
Archived-At: <https://mailarchive.ietf.org/arch/msg/curdle/ISiZqdJeLNoXhWTiPA3OESHHB5Y>
Subject: Re: [Curdle] comments on draft-ietf-curdle-rsa-sha2-03.txt
X-BeenThere: curdle@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "List for discussion of potential new security area wg." <curdle.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/curdle>, <mailto:curdle-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/curdle/>
List-Post: <mailto:curdle@ietf.org>
List-Help: <mailto:curdle-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/curdle>, <mailto:curdle-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 08 Apr 2017 11:20:53 -0000
I tend to agree. While it is plausible that PSS avoids providing implementers an easy way to incorrectly verify a signature, I am not in favor of banning working concepts because they've been implemented incorrectly. By that token, the most important proviso we should put in the drafts is: "Do not, under any circumstances, implement this protocol in a memory unsafe language, such as C or C++"... On Fri, Apr 7, 2017 at 9:42 PM, Peter Gutmann <pgut001@cs.auckland.ac.nz> wrote: > Watson Ladd <watsonbladd@gmail.com> writes: > > >I strongly object. PKCS 1.5 signature verification has a long and > inglorious > >history of exploitation. PSS does not. > > That's because nothing uses PSS, so there's no chance to exploit it. By > that > argument we should all be using IYOPS, which not only isn't implemented but > hasn't even been defined yet, making it even more immune to exploitation. > > The problem with PKCS #1 was that people implemented it wrong in a variety > of > ways, if you follow the spec (encode-then-memcmp) then it's perfectly > sound. > Given that most PKCS #1 implementations should by now have been fixed (it's > been what, 20 years) while if we moved to PSS we'd be starting again from > scratch with everyone getting the chance to mess things up in different > ways, > PSS is at best no better than PKCS #1, at worst a lot worse. > > Peter. >
- Re: [Curdle] comments on draft-ietf-curdle-rsa-sh… Daniel Migault
- Re: [Curdle] comments on draft-ietf-curdle-rsa-sh… Watson Ladd
- Re: [Curdle] comments on draft-ietf-curdle-rsa-sh… denis bider
- Re: [Curdle] comments on draft-ietf-curdle-rsa-sh… Peter Gutmann
- Re: [Curdle] comments on draft-ietf-curdle-rsa-sh… denis bider
- Re: [Curdle] comments on draft-ietf-curdle-rsa-sh… Daniel Migault
- Re: [Curdle] comments on draft-ietf-curdle-rsa-sh… Mark D. Baushke
- [Curdle] comments on draft-ietf-curdle-rsa-sha2-0… Daniel Migault
- Re: [Curdle] comments on draft-ietf-curdle-rsa-sh… denis bider (Bitvise)
- Re: [Curdle] comments on draft-ietf-curdle-rsa-sh… Daniel Migault
- Re: [Curdle] comments on draft-ietf-curdle-rsa-sh… denis bider
- Re: [Curdle] comments on draft-ietf-curdle-rsa-sh… Peter Gutmann
- Re: [Curdle] comments on draft-ietf-curdle-rsa-sh… Peter Gutmann
- Re: [Curdle] comments on draft-ietf-curdle-rsa-sh… denis bider
- Re: [Curdle] comments on draft-ietf-curdle-rsa-sh… Daniel Migault
- Re: [Curdle] comments on draft-ietf-curdle-rsa-sh… Ilari Liusvaara
- Re: [Curdle] comments on draft-ietf-curdle-rsa-sh… denis bider
- Re: [Curdle] comments on draft-ietf-curdle-rsa-sh… Daniel Migault
- Re: [Curdle] comments on draft-ietf-curdle-rsa-sh… Watson Ladd
- Re: [Curdle] comments on draft-ietf-curdle-rsa-sh… Daniel Migault