Re: [perpass] RSA-OAEP

Richard Barnes <rlb@ipv.sx> Wed, 20 November 2013 16:09 UTC

Return-Path: <rlb@ipv.sx>
X-Original-To: perpass@ietfa.amsl.com
Delivered-To: perpass@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 405811AE3FC for <perpass@ietfa.amsl.com>; Wed, 20 Nov 2013 08:09:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.977
X-Spam-Level:
X-Spam-Status: No, score=-1.977 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7] 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 ordkWgkSzh_d for <perpass@ietfa.amsl.com>; Wed, 20 Nov 2013 08:09:43 -0800 (PST)
Received: from mail-oa0-f42.google.com (mail-oa0-f42.google.com [209.85.219.42]) by ietfa.amsl.com (Postfix) with ESMTP id D6F141AE01B for <perpass@ietf.org>; Wed, 20 Nov 2013 08:09:42 -0800 (PST)
Received: by mail-oa0-f42.google.com with SMTP id i4so5132030oah.15 for <perpass@ietf.org>; Wed, 20 Nov 2013 08:09:36 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=53O5nc+GGwAjzGDqRmmr9K0KDG5jAqHTn/QF227dT/A=; b=LpgLt3X+K9AanLycOUG87Dr7evDgTnTNd9JLOj/fIN0rZlxxYU2A1Nwl+Uwe2aU3W8 UVOM52BSrH/d8rQOWFLyHiIN+tfA9mmrzgA4Jx3IWCqbFF84WxTyO/6MUnheNAOAcPkd 3IhWNEpApssMIMz+eedAztSJhcx+r4yqDbsbZoZSMsCD5s2LkW/BrqGiRNHxE/QlU9qU x7GZCivNER/paRbgvhYzwxJac5C72PDwA2c2Jtq4xOCmt7l4wZfBd4LX1qQ6Lmw5wpyA 8mFQmaTb35x2XzJ0g44YXxxr0PwooQJVcj9zDJUqKzScIyxl4eytgOWRuxpLIEaGdZMx 3Y7w==
X-Gm-Message-State: ALoCoQkNBorW0VUDREMCQ5GbnYPSb3Ou+jrac6iUE3VtEC3BUnx7RgogS4V5Xq+0HK5jvM9DPsHI
MIME-Version: 1.0
X-Received: by 10.60.63.141 with SMTP id g13mr1120812oes.60.1384963776408; Wed, 20 Nov 2013 08:09:36 -0800 (PST)
Received: by 10.60.31.74 with HTTP; Wed, 20 Nov 2013 08:09:36 -0800 (PST)
In-Reply-To: <C9843EE0-93F1-4707-8911-D8A2AC334AC8@vigilsec.com>
References: <C9843EE0-93F1-4707-8911-D8A2AC334AC8@vigilsec.com>
Date: Wed, 20 Nov 2013 11:09:36 -0500
Message-ID: <CAL02cgTKVuA1wETubwLf_u=rYEEa=K8_JxNcFbC169V17A53wg@mail.gmail.com>
From: Richard Barnes <rlb@ipv.sx>
To: Russ Housley <housley@vigilsec.com>
Content-Type: multipart/alternative; boundary="001a11c1db34eb7ed104eb9e0196"
Cc: perpass <perpass@ietf.org>
Subject: Re: [perpass] RSA-OAEP
X-BeenThere: perpass@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "The perpass list is for IETF discussion of pervasive monitoring. " <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: Wed, 20 Nov 2013 16:09:45 -0000

What are you proposing be done, besides supporting OAEP in new specs or
back-porting it to old ones?  In order to make people use OAEP, we would
need to call in the protocol police.


On Wed, Nov 20, 2013 at 10:49 AM, Russ Housley <housley@vigilsec.com> wrote:

> We have known for a ver long time that PKCS #1 Version 1.5 (see RFC 2313)
> is vulnerable to adaptive chosen ciphertext attacks when applied for
> encryption purposes.  Exploitation reveals the result of a particular RSA
> decryption, requires access to an oracle which will respond to a hundreds
> of thousands of ciphertexts), which are constructed adaptively in response
> to previously-received replies providing information on the successes or
> failures of attempted decryption operations.  As a result, the attack
> appears significantly less feasible to perpetrate in store-and-forward
> environments than for interactive ones.
>
> PKCS #1 Version 2.0 and Version 2.1 (see RFC 3447) include RSA-OAEP to
> address this situation, but we have seen very little movement toward
> RSA-OAEP.  While we are reviewing algorithm choices in light of the
> pervasive surveillance situation, I think we should take the time to
> address known vulnerabilities like this one.  If we don't, then we are
> leaving an partially open door for a well funded attacker.
>
> Russ
> _______________________________________________
> perpass mailing list
> perpass@ietf.org
> https://www.ietf.org/mailman/listinfo/perpass
>