IETF Logo Mail Archive

Re: [OAUTH-WG] WGLC for "OAuth 2.0 Security Best Current Practice"

Hans Zandbelt <hans.zandbelt@zmartzone.eu> Fri, 08 November 2019 13:37 UTC

Return-Path: <hans.zandbelt@zmartzone.eu>
X-Original-To: oauth@ietfa.amsl.com
Delivered-To: oauth@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 263CE12006F for <oauth@ietfa.amsl.com>; Fri, 8 Nov 2019 05:37:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=zmartzone-eu.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 40cT-s5dAUHV for <oauth@ietfa.amsl.com>; Fri, 8 Nov 2019 05:37:30 -0800 (PST)
Received: from mail-qk1-x72b.google.com (mail-qk1-x72b.google.com [IPv6:2607:f8b0:4864:20::72b]) (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 3DDF812003F for <oauth@ietf.org>; Fri, 8 Nov 2019 05:37:30 -0800 (PST)
Received: by mail-qk1-x72b.google.com with SMTP id q70so5219982qke.12 for <oauth@ietf.org>; Fri, 08 Nov 2019 05:37:30 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=zmartzone-eu.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=rvXQ/N9lJvedaIPbh+gdfNgifwbOzdddGjlrXC5WMvI=; b=tVDUZmXIAMtgVCBFdbysdSkOmHzYCz0wJya0cgcWDAKfHXVbDT/O3XWj23PhkjNT/D 0cPB1ucmyhFbPBzvdnrM4ujhqZFkJgS49MBWYnO3m8L2jHJWMhtd2qxbaoN8pmjnkBN5 S2Z1kQMZEoemXcfGDHMlpgVLQJtBahol4pdnX4aj0qDWoJxzUAWxQ4QBAQHoTljZxsQQ qmzIF2tqOkRNZsYIxdgSTLRDELGWyoWZo74e5vOx/ecml/DcCfRUZaNx5Czgy54XWeSe +SZ6rpLUBL3YvV7l54paHcfieS21/XsuoYPK4027s8xUTQ9W53FNCcDl48novSeDgDq0 ga/w==
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:cc; bh=rvXQ/N9lJvedaIPbh+gdfNgifwbOzdddGjlrXC5WMvI=; b=nSTzoW8baZ2USTEjjgpLMOfIADuO6KyCUUeXhqvU97jfB+PtkwcQseSmraW1YXbLcF oNPW/qcw1kprQdejK5kQAY9HgfIZ6SWN93OnWpU4qajeTN7rDsr5qo+Mil5oETXjd6Ys 9tuodt5hsfsEKxQ/1prCpa9ArOBY5TldMbCQoQfNCF5z3Lt+noo0z5J556nkEVueQBMO ISoBmOXfQHelTY5P60l/BNEpfVHGf17AfCTPOjh71pKKGOIJUmqt0SE4mzVXK9a0ewOV U5Su8JVUNI6w2JBE7Kk7AEul2TQnn30Bw+9wobpcXYn+r5KQGtxoqrJ/4azkG3DIoRp8 Y4vQ==
X-Gm-Message-State: APjAAAX7vewr4jTYX4WrZUTB06YvyANOIetG9vHMS45p1cHFPUTAqVp2 Ya9toMTEx2txrCi22MJjyWT43mbDDy6+A3/Bbkn0cw==
X-Google-Smtp-Source: APXvYqxkBsHyfqsfqgB8byuwQRRbJy0y61UwFXkVWmN/fknJ1F0tlmRO+LnbqfEbMVhMp5qurjqTPMk8gvW5l29XT9g=
X-Received: by 2002:a37:a5c7:: with SMTP id o190mr8902957qke.478.1573220249143; Fri, 08 Nov 2019 05:37:29 -0800 (PST)
MIME-Version: 1.0
References: <VI1PR08MB5360FBBAF0D3A38BDBED618BFA790@VI1PR08MB5360.eurprd08.prod.outlook.com> <CAMVRk++o2MdndK37FfADzEZJx988o=PvPWN_mhdgDK=OU1dtow@mail.gmail.com> <3ECDBBC5-F183-4227-857A-A95C53C74274@mit.edu> <d021c84a-36f3-f371-2903-2b6051ee654f@free.fr> <8324a1d3-2fe8-430c-facc-1f3c5d7db260@danielfett.de> <21a36a19-1f24-25d9-9478-1e282a1bea19@free.fr> <CA+iA6uhqVf9B2VxzS7cFx_ATSymB9gsAk0ebpjdv99ymW6RjXA@mail.gmail.com> <ff668a74-52f9-3ac9-acf0-ad3e27e98ea9@free.fr>
In-Reply-To: <ff668a74-52f9-3ac9-acf0-ad3e27e98ea9@free.fr>
From: Hans Zandbelt <hans.zandbelt@zmartzone.eu>
Date: Fri, 08 Nov 2019 14:37:18 +0100
Message-ID: <CA+iA6uioyqExsnONWEVYGyU-OSgqLcbkTMa+CyyjyVZEunaEqw@mail.gmail.com>
To: Denis <denis.ietf@free.fr>
Cc: "oauth@ietf.org" <oauth@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000001aa1b30596d5e234"
Archived-At: <https://mailarchive.ietf.org/arch/msg/oauth/gOidyp0k88N-54rD0w4tRX2ylAY>
Subject: Re: [OAUTH-WG] WGLC for "OAuth 2.0 Security Best Current Practice"
X-BeenThere: oauth@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: OAUTH WG <oauth.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/oauth>, <mailto:oauth-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/oauth/>
List-Post: <mailto:oauth@ietf.org>
List-Help: <mailto:oauth-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/oauth>, <mailto:oauth-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 08 Nov 2019 13:37:33 -0000

screenshot...

Hans.

On Fri, Nov 8, 2019 at 2:13 PM Denis <denis.ietf@free.fr> wrote:

> Hello Hans,
>
> You wrote:
>
> one client can always share the protected data with another client once
> retrieved, regardless of pop or secure elements
>
> No, there exist means that prevent a client to share the protected data
> with another client , simply because the client cannot access to it.
> The protected data is placed inside the secure element and thus a client
> has no way to extract it for the benefit of another client.
>
> The protected data is used by the secure element in such a way so that it
> cannot be used for the benefit of another user.
>
> But we are already in the field of the solutions and no more in the field
> of the requirements.
>
> Denis
>
>
> Hans.
>
> On Fri, Nov 8, 2019 at 8:38 AM Denis <denis.ietf@free.fr> wrote:
>
>> Daniel,
>>
>> No. It is not a correct summary. One client can allow another client to
>> get an access token that belongs to it.
>> The key point is that a software only solution can't prevent this
>> collaborative attack and since, at this time,
>> the OAuth WG is not considering the use of secure elements, the attack
>> cannot be countered.
>>
>> Please have a look at:
>> https://www.ietf.org/mail-archive/web/oauth/current/msg16767.html
>>
>> Denis
>>
>>
>> Hi Denis,
>>
>> Am 07.11.19 um 09:16 schrieb Denis:
>>
>>
>>        *Whatever kind of cryptographic is being used, when two users
>> collaborate, a software-only solution will be unable to prevent the
>> transmission *
>> *       of an attribute of a user that possess it to another user that
>> does not possess it. *
>>
>> To stay in OAuth lingo, what you are saying is: Two collaborating clients
>> can exchange their access tokens and use them.
>>
>> Is that a correct summary of your attack?
>>
>> -Daniel
>>
>>
>>
>> _______________________________________________
>> OAuth mailing listOAuth@ietf.orghttps://www.ietf.org/mailman/listinfo/oauth
>>
>>
>> _______________________________________________
>> OAuth mailing list
>> OAuth@ietf.org
>> https://www.ietf.org/mailman/listinfo/oauth
>>
>
>
> --
> hans.zandbelt@zmartzone.eu
> ZmartZone IAM - www.zmartzone.eu
>
>
>

-- 
hans.zandbelt@zmartzone.eu
ZmartZone IAM - www.zmartzone.eu

v2.23.0 | Report a Bug | By Email