Re: [OAUTH-WG] Request sent to http: instead of https:`

Lukas Rosenstock <lr@lukasrosenstock.net> Thu, 14 October 2010 08:21 UTC

Return-Path: <lr@lukasrosenstock.net>
X-Original-To: oauth@core3.amsl.com
Delivered-To: oauth@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 978E13A681E for <oauth@core3.amsl.com>; Thu, 14 Oct 2010 01:21:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.578
X-Spam-Level:
X-Spam-Status: No, score=-1.578 tagged_above=-999 required=5 tests=[AWL=0.399, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aw6KjMPWiFGu for <oauth@core3.amsl.com>; Thu, 14 Oct 2010 01:20:59 -0700 (PDT)
Received: from mail-qy0-f172.google.com (mail-qy0-f172.google.com [209.85.216.172]) by core3.amsl.com (Postfix) with ESMTP id 9E4423A67CF for <oauth@ietf.org>; Thu, 14 Oct 2010 01:20:59 -0700 (PDT)
Received: by qyk8 with SMTP id 8so1505451qyk.10 for <oauth@ietf.org>; Thu, 14 Oct 2010 01:22:16 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.224.199.67 with SMTP id er3mr7444623qab.37.1287044518569; Thu, 14 Oct 2010 01:21:58 -0700 (PDT)
Received: by 10.229.190.210 with HTTP; Thu, 14 Oct 2010 01:21:58 -0700 (PDT)
In-Reply-To: <90C41DD21FB7C64BB94121FBBC2E72343D4691FAAB@P3PW5EX1MB01.EX1.SECURESERVER.NET>
References: <AANLkTikO0oqudUchUnpW0vSsXe0k6QKkJpxjFUU+b413@mail.gmail.com> <90C41DD21FB7C64BB94121FBBC2E72343D4691FAAB@P3PW5EX1MB01.EX1.SECURESERVER.NET>
Date: Thu, 14 Oct 2010 10:21:58 +0200
Message-ID: <AANLkTik5XHaXBfV3y-vGBBrKBEWh=BUeL65Z23+-ERSB@mail.gmail.com>
From: Lukas Rosenstock <lr@lukasrosenstock.net>
To: Eran Hammer-Lahav <eran@hueniverse.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: "oauth@ietf.org" <oauth@ietf.org>
Subject: Re: [OAUTH-WG] Request sent to http: instead of https:`
X-BeenThere: oauth@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: OAUTH WG <oauth.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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, 14 Oct 2010 08:21:00 -0000

Facebook doesn't invalidate the token.
Isn't invalidating tokens incompatible with architectures which use
self-contained (cryptographic) tokens instead of random strings?! If
so, making this a requirement would force the server developers to
implement a TRL (token revocation list, similar to a CRL) where every
token - even those cryptographically valid - would need to be checked
against. While this would be great from a security perspective, it
might be impractical.

2010/10/14 Eran Hammer-Lahav <eran@hueniverse.com>om>:
> Hopefully you also invalidate the token (if bearer) since it was send over an insecure channel.
>
> EHL
>
>> -----Original Message-----
>> From: oauth-bounces@ietf.org [mailto:oauth-bounces@ietf.org] On Behalf
>> Of Breno
>> Sent: Wednesday, October 13, 2010 11:31 AM
>> To: oauth@ietf.org
>> Subject: [OAUTH-WG] Request sent to http: instead of https:`
>>
>> Suppose server A documents that their endpoint X is at
>> https://server.example.com/x; there's no service at the corresponding http
>> location for security reasons.
>>
>> Client developer fatfingers URL as http://server.example.com/x
>>
>> What is the correct response? I understand that this is out of scope for the
>> spec, but maybe there's agreement on some guidance?
>>
>> One thing one shouldn't do is serve a 302 here; it would allow defective
>> clients to remain unpatched.
>>
>> My preference is to simply return a bare 403 or 404 here -- after all the
>> endpoint does not exist (404) or if one uses the convention that resources at
>> http/https are usually identical, then http is a non-authorized method to
>> access the resource (403).
>>
>> Thoughts?
>>
>> --
>> Breno de Medeiros
>> _______________________________________________
>> OAuth mailing list
>> OAuth@ietf.org
>> https://www.ietf.org/mailman/listinfo/oauth
> _______________________________________________
> OAuth mailing list
> OAuth@ietf.org
> https://www.ietf.org/mailman/listinfo/oauth