IETF Logo Mail Archive

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

William Mills <wmills@yahoo-inc.com> Thu, 14 October 2010 00:04 UTC

Return-Path: <wmills@yahoo-inc.com>
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 DEC0F3A69EF for <oauth@core3.amsl.com>; Wed, 13 Oct 2010 17:04:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -17.494
X-Spam-Level:
X-Spam-Status: No, score=-17.494 tagged_above=-999 required=5 tests=[AWL=0.104, BAYES_00=-2.599, NO_RDNS_DOTCOM_HELO=0.001, USER_IN_DEF_WHITELIST=-15]
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 GJ5WCTUatcX2 for <oauth@core3.amsl.com>; Wed, 13 Oct 2010 17:04:02 -0700 (PDT)
Received: from mrout2.yahoo.com (mrout2.yahoo.com [216.145.54.172]) by core3.amsl.com (Postfix) with ESMTP id 3963C3A69B0 for <oauth@ietf.org>; Wed, 13 Oct 2010 17:04:02 -0700 (PDT)
Received: from SP2-EX07CAS05.ds.corp.yahoo.com (sp2-ex07cas05.corp.sp2.yahoo.com [98.137.59.39]) by mrout2.yahoo.com (8.14.4/8.14.4/y.out) with ESMTP id o9E04qkO023799; Wed, 13 Oct 2010 17:04:52 -0700 (PDT)
Received: from SP2-EX07VS06.ds.corp.yahoo.com ([98.137.59.24]) by SP2-EX07CAS05.ds.corp.yahoo.com ([98.137.59.39]) with mapi; Wed, 13 Oct 2010 17:04:52 -0700
From: William Mills <wmills@yahoo-inc.com>
To: Breno <breno.demedeiros@gmail.com>, Jeff Lindsay <progrium@twilio.com>
Date: Wed, 13 Oct 2010 17:04:51 -0700
Thread-Topic: [OAUTH-WG] Request sent to http: instead of https:`
Thread-Index: ActrMWEod6MO6T69RqetfsTo6OBRuwAAdZmA
Message-ID: <FFDFD7371D517847AD71FBB08F9A3156254C4A752A@SP2-EX07VS06.ds.corp.yahoo.com>
References: <AANLkTikO0oqudUchUnpW0vSsXe0k6QKkJpxjFUU+b413@mail.gmail.com> <90C41DD21FB7C64BB94121FBBC2E72343D4691FAAB@P3PW5EX1MB01.EX1.SECURESERVER.NET> <AANLkTimS-iMB3Bym968imAWicpSa6D_MSdJNW+NytD_Z@mail.gmail.com> <AANLkTimY3aOcb-SWRD6woj7Zfe4Zd3v_QWb+oE-Wx4v8@mail.gmail.com>
In-Reply-To: <AANLkTimY3aOcb-SWRD6woj7Zfe4Zd3v_QWb+oE-Wx4v8@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
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 00:04:03 -0000

This rather implies that we're specifying running a full server on port 80 as a "stupid detector".  We should tread carefully here.

> +1 for language in the spec describing how to handle this case
> 
> On Wed, Oct 13, 2010 at 4:12 PM, Jeff Lindsay <progrium@twilio.com>
> wrote:
> >> Hopefully you also invalidate the token (if bearer) since it was
> send over
> >> an insecure channel.
> >
> > Excuse my naivety, but perhaps that's worth putting in the spec?

v2.23.0 | Report a Bug | By Email