Re: [OAUTH-WG] OAuth & Authentication: What can go wrong?
John Bradley <ve7jtb@ve7jtb.com> Thu, 11 September 2014 23:30 UTC
Return-Path: <ve7jtb@ve7jtb.com>
X-Original-To: oauth@ietfa.amsl.com
Delivered-To: oauth@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 62DC71A0176 for <oauth@ietfa.amsl.com>; Thu, 11 Sep 2014 16:30:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level:
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] 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 XQm1_fgNwxwb for <oauth@ietfa.amsl.com>; Thu, 11 Sep 2014 16:30:57 -0700 (PDT)
Received: from mail-qg0-f41.google.com (mail-qg0-f41.google.com [209.85.192.41]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3A9231A0164 for <oauth@ietf.org>; Thu, 11 Sep 2014 16:30:57 -0700 (PDT)
Received: by mail-qg0-f41.google.com with SMTP id a108so8099939qge.14 for <oauth@ietf.org>; Thu, 11 Sep 2014 16:30:56 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:references:mime-version:in-reply-to:content-type :content-transfer-encoding:message-id:cc:from:subject:date:to; bh=VxJ461wNlArWHfetUsD5rW+aSZ+O312dYJRXJKFvcWk=; b=VIA8VImyCqKtn3/HoRxSqSWK/Ra4P+gWLdJR6PahqwbThcNnULTuOPnoGK0KqbdgCf UxgfO97cq9MVsd8gvgd91eWtG0HIyvhImHGNBC+H63g0TeJIDOHv79NcmdDfmPP/vSQX gLSj7F5jbsC97j8KiK/e8L3ANjPwMN79hPiv6ryKMCI7PovTy1idLClJhV5r5rIDsTvI bFDPx1CZ/yc5ys/YlH4/eVg7FNPy9nZUEHGXbZnkC+yApYWHn/nnYnb+PqpD/EAmJBFG Qxe2jPe5zHrf3l+5cdiQ9+IxVxROQEjLJjcSd/ps9H1oVieB/roPoe5yu1b5O+GkjMFT 2MXQ==
X-Gm-Message-State: ALoCoQkb61dPLqXjNsM/bXaWooaZSes8lOIIqV2uVJtycQLW9RbY+DDYYXrFg1z2ShIhsJGpl0XN
X-Received: by 10.224.131.7 with SMTP id v7mr3434904qas.5.1410478255987; Thu, 11 Sep 2014 16:30:55 -0700 (PDT)
Received: from [10.236.53.63] ([201.220.243.15]) by mx.google.com with ESMTPSA id x6sm1771259qas.27.2014.09.11.16.30.53 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 11 Sep 2014 16:30:54 -0700 (PDT)
References: <54122280.1030609@gmx.net> <1a2eb1cb9138414c83c258a73f92e413@BLUPR03MB309.namprd03.prod.outlook.com> <CABzCy2DcPo0fiwkSq=DYyCJo_r+CWimp_25ejtZWgQgACu7nDg@mail.gmail.com>
Mime-Version: 1.0 (1.0)
In-Reply-To: <CABzCy2DcPo0fiwkSq=DYyCJo_r+CWimp_25ejtZWgQgACu7nDg@mail.gmail.com>
Content-Type: multipart/signed; micalg="sha1"; boundary="Apple-Mail-A9896C7B-9325-4011-9DFF-92BF8D80F023"; protocol="application/pkcs7-signature"
Content-Transfer-Encoding: 7bit
Message-Id: <38674129-C06F-4C72-86A1-A942E7D71325@ve7jtb.com>
X-Mailer: iPhone Mail (11D257)
From: John Bradley <ve7jtb@ve7jtb.com>
Date: Thu, 11 Sep 2014 20:30:50 -0300
To: Nat Sakimura <sakimura@gmail.com>
Archived-At: http://mailarchive.ietf.org/arch/msg/oauth/cgLlug6uqAc6akAWv8odBEBhurY
Cc: Derek Atkins <derek@ihtfp.com>, "oauth@ietf.org" <oauth@ietf.org>
Subject: Re: [OAUTH-WG] OAuth & Authentication: What can go wrong?
X-BeenThere: oauth@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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, 11 Sep 2014 23:30:59 -0000
And me Sent from my iPhone > On Sep 11, 2014, at 7:49 PM, Nat Sakimura <sakimura@gmail.com> wrote: > > Add me, too. > > 2014-09-12 7:32 GMT+09:00 Anthony Nadalin <tonynad@microsoft.com>: >> Add me >> >> -----Original Message----- >> From: OAuth [mailto:oauth-bounces@ietf.org] On Behalf Of Hannes Tschofenig >> Sent: Thursday, September 11, 2014 3:30 PM >> To: oauth@ietf.org >> Cc: Derek Atkins >> Subject: [OAUTH-WG] OAuth & Authentication: What can go wrong? >> >> Hi all, >> >> at the last IETF meeting Mike gave a presentation about the draft-hunt-oauth-v2-user-a4c and the conclusion following the discussion was to discuss the problems that happen when OAuth gets used for authentication. >> >> The goal of this effort is to document the problems in an informational document. >> >> Conference calls could start in about 2 weeks and we would like to know who would be interested to participate in such a discussion. >> >> Please drop us a private mail so that we can find suitable dates/times. >> >> Ciao >> Hannes & Derek >> >> _______________________________________________ >> OAuth mailing list >> OAuth@ietf.org >> https://www.ietf.org/mailman/listinfo/oauth > > > > -- > Nat Sakimura (=nat) > Chairman, OpenID Foundation > http://nat.sakimura.org/ > @_nat_en > _______________________________________________ > OAuth mailing list > OAuth@ietf.org > https://www.ietf.org/mailman/listinfo/oauth
- [OAUTH-WG] OAuth & Authentication: What can go wr… Hannes Tschofenig
- Re: [OAUTH-WG] OAuth & Authentication: What can g… Anthony Nadalin
- Re: [OAUTH-WG] OAuth & Authentication: What can g… Nat Sakimura
- Re: [OAUTH-WG] OAuth & Authentication: What can g… Phil Hunt
- Re: [OAUTH-WG] OAuth & Authentication: What can g… John Bradley
- Re: [OAUTH-WG] OAuth & Authentication: What can g… Gil Kirkpatrick
- Re: [OAUTH-WG] OAuth & Authentication: What can g… Antonio Sanso
- Re: [OAUTH-WG] OAuth & Authentication: What can g… Tirumaleswar Reddy (tireddy)
- Re: [OAUTH-WG] OAuth & Authentication: What can g… Torsten Lodderstedt