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

Daniel Fett <fett@danielfett.de> Thu, 07 November 2019 13:24 UTC

Return-Path: <fett@danielfett.de>
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 D069312083C for <oauth@ietfa.amsl.com>; Thu, 7 Nov 2019 05:24:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=danielfett.de
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 mMTcA9Kk-Npe for <oauth@ietfa.amsl.com>; Thu, 7 Nov 2019 05:24:58 -0800 (PST)
Received: from d3f.me (redstone.d3f.me [5.9.29.41]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3580F120864 for <oauth@ietf.org>; Thu, 7 Nov 2019 05:24:57 -0800 (PST)
Received: from authenticated-user (PRIMARY_HOSTNAME [PUBLIC_IP]) by d3f.me (Postfix) with ESMTPA id 37E8120BCA for <oauth@ietf.org>; Thu, 7 Nov 2019 13:24:55 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=danielfett.de; s=dkim; t=1573133095; h=from:from:sender:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:mime-version:mime-version: content-type:content-type:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=WHfa3nXkzq6K8NWLwPD71G7oJhMjio27lZR/V4xNuJQ=; b=E0Si1VGUcPIVn4jFDnkneFWadO2OK0pb+esq6r42auXtJ5C0T0qEK8O7F1GSmtLtT58H6W 19Xu+OyY07eXq/rj0aFGp9J82pH6P19TdjOM7tWu86xqwHF6G4SipOfBlX+VYRbzYk8Iac r413QGBC95JQ94AOg4D70k0fz/aiG7w=
To: oauth@ietf.org
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>
From: Daniel Fett <fett@danielfett.de>
Message-ID: <8324a1d3-2fe8-430c-facc-1f3c5d7db260@danielfett.de>
Date: Thu, 07 Nov 2019 14:24:54 +0100
MIME-Version: 1.0
In-Reply-To: <d021c84a-36f3-f371-2903-2b6051ee654f@free.fr>
Content-Type: multipart/alternative; boundary="------------153C61E1EF8929F9ECEB272B"
Content-Language: de-DE
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=danielfett.de; s=dkim; t=1573133095; h=from:from:sender:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:mime-version:mime-version: content-type:content-type:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=WHfa3nXkzq6K8NWLwPD71G7oJhMjio27lZR/V4xNuJQ=; b=gZGyDWerKqW+4TH7lIgfZibWWz4nSvrAzlSGHQhnUPQp5FFY4skQGPsyyzI7rHmFYgbXoz lKyVwMNaJs4pX4ZuA+TbTpk9hPAbwwDwjw7bnzkdqV+ja/z3aZbHwDxhMMquCzHEoxyPi2 dzVZ9fZDL0O7hF82vrPEBTqQAobayZE=
ARC-Seal: i=1; s=dkim; d=danielfett.de; t=1573133095; a=rsa-sha256; cv=none; b=X+5N/QI4JnxOddRNwBZhBNzzk0mTQ6ZNfkyNH+TfN+m7vLinc95wsF3VrPo/trQgpXu78r5NDVY2qMUMxO2R/pcPTTO2v+JoGjWX3O1De+V86GbgULtPv8HCPwcdWtB2NW37wFmC5qOgIuBj/zQMHL3l27LceveuELen1GJliyo=
ARC-Authentication-Results: i=1; d3f.me; auth=pass smtp.auth=fett@danielfett.de smtp.mailfrom=fett@danielfett.de
Authentication-Results: d3f.me; auth=pass smtp.auth=fett@danielfett.de smtp.mailfrom=fett@danielfett.de
X-Spamd-Bar: /
Archived-At: <https://mailarchive.ietf.org/arch/msg/oauth/fOMfbuUNljLK2hi4f9qXseiJMUw>
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: Thu, 07 Nov 2019 13:25:08 -0000

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