Re: [Cfrg] Cfrg Digest, Vol 181, Issue 12

Kyle Den Hartog <kyle.denhartog@mattr.global> Fri, 08 May 2020 03:06 UTC

Return-Path: <kyle.denhartog@mattr.global>
X-Original-To: cfrg@ietfa.amsl.com
Delivered-To: cfrg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C81273A0112 for <cfrg@ietfa.amsl.com>; Thu, 7 May 2020 20:06:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.896
X-Spam-Level:
X-Spam-Status: No, score=-1.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=mattr-global.20150623.gappssmtp.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 Ku5itVsnKb59 for <cfrg@ietfa.amsl.com>; Thu, 7 May 2020 20:06:08 -0700 (PDT)
Received: from mail-lf1-x12f.google.com (mail-lf1-x12f.google.com [IPv6:2a00:1450:4864:20::12f]) (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 16CE43A0544 for <cfrg@irtf.org>; Thu, 7 May 2020 20:06:07 -0700 (PDT)
Received: by mail-lf1-x12f.google.com with SMTP id a4so236884lfh.12 for <cfrg@irtf.org>; Thu, 07 May 2020 20:06:07 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mattr-global.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=QbO8E8FQFMxvWPRCUA7TJqrlXdy8Kf8yqzF4ICRKrNc=; b=jPLIG4sLAx2TlccOY9hldPHOqFEhXraSu7OaY5NHwLwZKQZbEYnn+Xva/Yd5TDp0ez D9cw3IsrgwgJ9DXHMWLUHY1w0YiayHI6998/B9Cw6cFPKJ+47gDBbTuIxe1cEo59uXFt HEBTtUQdLTuaf9ZKZOhXAAYLhZ6MRuAqjINSj3kw8UMVQDIxqwZQUXoYl1rI6ex2MSp6 WV+WOMXiH76Ftx81Dhp0WpyC3HTJryfAOakiAWLFW1Sr1jlZqj44+BeJr0AAzTYDddM7 swzFfI1jOZG4392TWBMomDhkz/zp2uDv9x4uv1raqXHdL7ejA5zf/NKNML+Yf6Bq0H20 m6UQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=QbO8E8FQFMxvWPRCUA7TJqrlXdy8Kf8yqzF4ICRKrNc=; b=DL9KCjFdrkWKHQKr26nJEIzcVDQGv6YhUgB5yxiXMRFYm6C3WYzln/6zf2a1XkHeL3 S1WqsVu0jAKRHC01mBp4g0P56KORKGpErSrxxDSc+kpRQEj+LOcv/ptToOOCaKYXd8mF eOs31pWI4Vd6KV4hZ+rPWNt7AcIjqCKnWDcuAKKfWQrfO+2dg64HmLUf0mnBCGcwGiDn iyg5NsPt1IJQLCjqo44GyPgaHd6KicRsvdEGUHigysyZiiCLt5NKfonyQvmDxh/d3Yax TUdC3uJlnTdjTzRI4K7GH288i4SZWAoIqr+eFA3dZAiuzJ0dG0I9skDVAqJndzVKjJ5H q4Vw==
X-Gm-Message-State: AOAM532J/dp53Lx19EYO9ggl1EgtnfQiSUvmYR9j4hLg/Ow1iK/eqXPr mjiyx+ozGFTv6Y0wnGSwN4WPWQOxfGttAvI76INraPQzKFaKpHBOgEvuKf7EIhp2CZ4t8mIBcG7 +DnEi1G7wBBn4d7MwPvn19rc=
X-Google-Smtp-Source: ABdhPJz/PLJHU4pma8rn5nCgC/cNVb4OoY1xulEH2OVCP2o9EVCsfZ+HdLY3ISehToAALHMZPiFgH9eHuTuW/MAYl/8=
X-Received: by 2002:ac2:4143:: with SMTP id c3mr372225lfi.131.1588907165740; Thu, 07 May 2020 20:06:05 -0700 (PDT)
MIME-Version: 1.0
References: <mailman.906.1588858769.8954.cfrg@irtf.org>
In-Reply-To: <mailman.906.1588858769.8954.cfrg@irtf.org>
From: Kyle Den Hartog <kyle.denhartog@mattr.global>
Date: Fri, 8 May 2020 15:05:54 +1200
Message-ID: <CAPHCqSyuCZySrsLEpg_aWE5zhkdSyTFBjQr8nwc8ehquMAiWwA@mail.gmail.com>
To: cfrg@irtf.org
Content-Type: multipart/alternative; boundary="000000000000320b2f05a51a4770"
Archived-At: <https://mailarchive.ietf.org/arch/msg/cfrg/jPR8FxpfiuzGR-VOovdSlZ2N9FQ>
Subject: Re: [Cfrg] Cfrg Digest, Vol 181, Issue 12
X-BeenThere: cfrg@irtf.org
X-Mailman-Version: 2.1.29
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: Fri, 08 May 2020 03:06:12 -0000

We're working to get the xchacha20poly1305 scheme added as well once
https://tools.ietf.org/html/draft-irtf-cfrg-xchacha-03 has been approved.
At the same time, we'll likely also register the chacha20poly1305 scheme as
well.
The draft that we've been working off to that is here:
https://tools.ietf.org/html/draft-amringer-jose-chacha-02

Also, my understanding is that the MLS spec is attempting to achieve
something very similar (sender anonymity to outside parties, while
encrypting to multiple recipients) with the HPKE spec. Is my understanding
correct that this property is shared there and would that be a route worth
taking for this? Of note, my company is the one who was looking to add
multi-recipient recipient support to the scheme and the original design
goal of using this would be to get sender anonymity to outside parties,
while also keeping repudiable authentication.

-Kyle

On Fri, May 8, 2020 at 1:41 AM <cfrg-request@irtf.org> wrote:

> Send Cfrg mailing list submissions to
>         cfrg@irtf.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
>         https://www.irtf.org/mailman/listinfo/cfrg
> or, via email, send a message with subject or body 'help' to
>         cfrg-request@irtf.org
>
> You can reach the person managing the list at
>         cfrg-owner@irtf.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Cfrg digest..."
>
>
> Today's Topics:
>
>    1. Re: Multi-recipient public key authenticated encryption
>       (pag225@cornell.edu)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Thu, 7 May 2020 09:39:11 -0400
> From: pag225@cornell.edu
> To: Neil Madden <neil.e.madden@gmail.com>
> Cc: Dan Brown <danibrown@blackberry.com>om>, CFRG <cfrg@irtf.org>
> Subject: Re: [Cfrg] Multi-recipient public key authenticated
>         encryption
> Message-ID: <E927FE4C-D888-450B-BD2C-3528D61D4D86@cornell.edu>
> Content-Type: text/plain; charset="utf-8"
>
> Oh ok, it?s too bad JOSE only supports GCM. You should be careful with
> using plain GCM in these multi-receiver settings - because it?s
> non-committing, it?s possible to craft a single ciphertext that different
> receivers decrypt to different plaintexts.
>
>
> > On May 7, 2020, at 7:28 AM, Neil Madden <neil.e.madden@gmail.com> wrote:
> >
> > ?Apologies, I forgot to respond to this. I think the ccAE approach is a
> nice way of solving the problem. Unfortunately, JOSE allows specifying the
> key exchange algorithm and AEAD cipher entirely independently so I have to
> have a solution that works with the AES-GCM based AEADs that are already
> part of the standard. But I will read these papers closely, because I do
> think the security notions are very similar to what I?m trying to achieve.
> >
> > ? Neil
> >
> >> On 28 Apr 2020, at 16:14, Paul Grubbs <pag225@cornell.edu> wrote:
> >>
> >> I think you can get away without the additional hash of the ciphertext
> entirely if you use a compactly committing AEAD (ccAE) scheme [1]. A ccAE
> has a two-part ciphertext C = (C1, C2) with the property that C2 is a
> binding commitment to the plaintext and key. At least intuitively, then,
> using C2 in the KDF prevents a receiver from modifying the message. (This
> is morally similar to including the MAC tag in the KDF, as suggested, but
> sidesteps questions about MAC security and may be faster if optimal-rate
> schemes like HFC [2] are used.) I haven't analyzed this construction
> formally, though, so take this advice with a bit of salt.
> >>
> >>
> >> [1] https://eprint.iacr.org/2017/664
> >> [2] https://eprint.iacr.org/2019/016.pdf
> >>
> >>> On Tue, Apr 28, 2020 at 8:30 AM Neil Madden <neil.e.madden@gmail.com>
> wrote:
> >>> Thanks, section 5 of the eprint is very useful. In that you discuss
> the solution of including the MAC tag in the KDF and you say that this
> requires collision resistance of the MAC, where I had previously assumed
> only 2nd preimage resistance would be enough. As I understand it, the
> potential attack is that if Charlie has access to an Alice-oracle by which
> he can get Alice to authenticate arbitrary messages to himself and Bob then
> he can use this to perform a collision search to find two messages with the
> same MAC tag (if the MAC is not collision resistant).
> >>>
> >>> I think this active attack would also apply to my proposed solution
> using a hash of the authenticated ciphertext as input to the KDF. So my
> assertion that 2nd preimage is enough is only valid for passive attacks,
> and full collision resistance would be needed in general. That also means
> that if I do pick SHA-256 to be consistent with existing use in JOSE then
> the security against such attacks would be limited to ~128 bit level.
> Perhaps that?s an incentive for me to also change the KDF in the scheme
> from JOSE?s existing Concat-KDF to HKDF with SHA-512.
> >>>
> >>> I think the same attack would also apply to saltpack [1], if I
> understand correctly? In saltpack a per-recipient MAC is calculated over a
> SHA-512 of the ciphertext.
> >>>
> >>> [1] https://saltpack.org/encryption-format-v2 (scroll down to Payload
> Packets)
> >>>
> >>> Best,
> >>>
> >>> Neil
> >>>
> >>>> On 27 Apr 2020, at 16:19, Dan Brown <danibrown@blackberry.com> wrote:
> >>>>
> >>>> Hi Neil,
> >>>> I too have encountered this interesting and well-known (perhaps not
> widely-known) problem.
> >>>> See https://eprint.iacr.org/2005/056.pdf. (Section 5).
> >>>> See https://tools.ietf.org/html/rfc3278#section-4.1.2 the very short
> ?note?.
> >>>>
> >>>> I forget the details of the various claimed past solutions, but will
> try to remember, maybe in a couple weeks.  Meanwhile, since the problem is
> fresh in your mind, and you might try to make sense the couple of old
> suggestions above, though I expect your knowledge has already advance past
> this old stuff.
> >>>>
> >>>> Best regards,
> >>>>
> >>>> Dan
> >>>>
> >>>> From: Cfrg <cfrg-bounces@irtf.org> On Behalf Of Neil Madden
> >>>> Sent: Monday, April 27, 2020 10:12 AM
> >>>> To: CFRG <cfrg@irtf.org>
> >>>> Subject: [Cfrg] Multi-recipient public key authenticated encryption
> >>>>
> >>>> Hi all,
> >>>>
> >>>> I am working on an enhancement to the JOSE standards and would like
> feedback from members of CFRG about solutions to a particular issue if any
> of you have time.
> >>>>
> >>>> In JOSE currently if you wish to create a message that has both
> confidentiality and sender authentication using public key cryptography
> then the only option is to both sign and then encrypt the message. This is
> expensive because it involves multiple passes over the message and results
> in a very bulky nested message structure with two layers of base64-encoding.
> >>>>
> >>>> Given that many uses of this sign-then-encrypt pattern do not require
> the strong security properties of signatures, I have proposed [1] a public
> key authenticated encryption mode based on NIST?s one-pass unified model
> from SP 800-56A. This avoids the nested structure and means that you don?t
> need multiple cryptographic primitives. The proposed algorithm uses two
> ECDH key agreements: one between the sender?s ephemeral private key and the
> recipient?s long-term public key; and a second between the two parties?
> long term keys. The two shared secrets are concatenated and passed through
> a KDF along with some context arguments. For a single recipient this
> achieves sender authentication (subject to replay), and the single
> recipient case is what I am primarily concerned about.
> >>>>
> >>>> (If you squint this is also roughly similar to the Noise framework
> ?K? one-way pattern, but my hands are waving quite a lot here).
> >>>>
> >>>> To support multiple recipients I copied the existing pattern used in
> JOSE?s ECDH-ES+A256KW algorithm family in which the message is encrypted
> using a random Content Encryption Key (CEK) and then the CEK is encrypted
> for each recipient using AES-KeyWrap with the ECDH-derived key. As I then
> mention in the security considerations this leads to any recipient being
> able to produce a forgery using that CEK and claim it came from the
> original sender:
> >>>>
> >>>>    When Key Agreement with Key Wrapping is used, with the same Content
> >>>>    Encryption Key (CEK) reused for multiple recipients, any of those
> >>>>    recipients can produce a new message that appears to come from the
> >>>>    original sender.  The new message will be indistinguishable from a
> >>>>    genuine message from the original sender to any of the other
> >>>>    participants.  To avoid this attack, the content SHOULD be
> encrypted
> >>>>    separately to each recipient with a unique CEK or a nested
> signature
> >>>>    over the content SHOULD be used.
> >>>>
> >>>> Because I am primarily interested in single-recipient use cases, this
> seemed like an acceptable trade-off. However, I have since been contacted
> by people who would like to use this draft for multi-recipient messages and
> would not like to fall back on a nested signature structure.
> >>>>
> >>>> An initial proposal was to solve this by simply including the MAC tag
> from the content encryption in either the per-recipient payload (encrypted
> using AES-KeyWrap) or as an additional context field to the KDF. But the
> MAC is computed using the CEK that is known to all recipients, so for this
> to be secure would require second preimage resistance of the MAC with a
> known key, which cannot be guaranteed for JOSE because it supports content
> encryption using AES-GCM for which second preimages can be trivially
> computed if you know the key.
> >>>>
> >>>> Assuming that a per-recipient MAC is too much overhead, an
> alternative would be to include a collision-resistant hash of entire
> ciphertext (and IV and associated data) in the KDF. This is unfortunate as
> it requires another pass over the entire message when we?ve already
> encrypted and MACed, but it appears to be a solution and at least is no
> more inefficient than the original signed-then-encrypted approach which
> also needs to hash the entire message.
> >>>>
> >>>> So two questions:
> >>>>
> >>>> 1. Is including a hash (e.g., SHA-512) of the ciphertext (assuming
> symmetric AE) in the per-recipient KDF calculation sufficient to prevent
> forgeries in the multi-recipient setting?
> >>>>
> >>>> 2. Are there more efficient alternatives that don?t assume 2nd
> preimage resistance of the underlying symmetric MAC?
> >>>>
> >>>> [1]: https://tools.ietf.org/html/draft-madden-jose-ecdh-1pu-03
> >>>>
> >>>> Kind regards,
> >>>>
> >>>> Neil Madden
> >>>> This transmission (including any attachments) may contain
> confidential information, privileged material (including material protected
> by the solicitor-client or other applicable privileges), or constitute
> non-public information. Any use of this information by anyone other than
> the intended recipient is prohibited. If you have received this
> transmission in error, please immediately reply to the sender and delete
> this information from your system. Use, dissemination, distribution, or
> reproduction of this transmission by unintended recipients is not
> authorized and may be unlawful.
> >>>
> >>> _______________________________________________
> >>> Cfrg mailing list
> >>> Cfrg@irtf.org
> >>> https://www.irtf.org/mailman/listinfo/cfrg
> >
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <
> https://mailarchive.ietf.org/arch/browse/cfrg/attachments/20200507/b484ef18/attachment.html
> >
>
> ------------------------------
>
> Subject: Digest Footer
>
> _______________________________________________
> Cfrg mailing list
> Cfrg@irtf.org
> https://www.irtf.org/mailman/listinfo/cfrg
>
>
> ------------------------------
>
> End of Cfrg Digest, Vol 181, Issue 12
> *************************************
>

-- 
This communication, including any attachments, is confidential. If you are 
not the intended recipient, you should not read it - please contact me 
immediately, destroy it, and do not copy or use any part of this 
communication or disclose anything about it. Thank you. Please note that 
this communication does not designate an information system for the 
purposes of the Electronic Transactions Act 2002.