IETF Logo Mail Archive

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

John Panzer <jpanzer@google.com> Thu, 14 October 2010 06:00 UTC

Return-Path: <jpanzer@google.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 5A91D3A6AC4 for <oauth@core3.amsl.com>; Wed, 13 Oct 2010 23:00:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.894
X-Spam-Level:
X-Spam-Status: No, score=-105.894 tagged_above=-999 required=5 tests=[AWL=0.083, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
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 FVxoR5ujXtra for <oauth@core3.amsl.com>; Wed, 13 Oct 2010 22:59:42 -0700 (PDT)
Received: from smtp-out.google.com (smtp-out.google.com [216.239.44.51]) by core3.amsl.com (Postfix) with ESMTP id AEA6B3A6AAE for <oauth@ietf.org>; Wed, 13 Oct 2010 22:59:35 -0700 (PDT)
Received: from wpaz17.hot.corp.google.com (wpaz17.hot.corp.google.com [172.24.198.81]) by smtp-out.google.com with ESMTP id o9E60rsN032457 for <oauth@ietf.org>; Wed, 13 Oct 2010 23:00:53 -0700
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=google.com; s=beta; t=1287036053; bh=0tOcoCfLaTlRDdd/XRLvpA5fRn0=; h=MIME-Version:In-Reply-To:References:Date:Message-ID:Subject:From: To:Cc:Content-Type:Content-Transfer-Encoding; b=e3fT6BPiYnc040Draak9zj8sievmBA1Yb23U/3jrZQj2j9mTnLIwBbBTQLIRRDclP 5xo56ZxBw3FkhqRhYXLbA==
Received: from gxk7 (gxk7.prod.google.com [10.202.11.7]) by wpaz17.hot.corp.google.com with ESMTP id o9E60blc015556 for <oauth@ietf.org>; Wed, 13 Oct 2010 23:00:52 -0700
Received: by gxk7 with SMTP id 7so1391425gxk.36 for <oauth@ietf.org>; Wed, 13 Oct 2010 23:00:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=beta; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=e5k61ew42Z1rKc2P4Y9FgdRvbuPmnMPdiOsHhUCdHpE=; b=JkIw3C99wEajbssMLl2W25nMNss2msroAW29cWNPc+MTLs3rvatsaSuW0E8rqmDwps xi3sXr/E6LdWXXNS8FbQ==
DomainKey-Signature: a=rsa-sha1; c=nofws; d=google.com; s=beta; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=mY1ibEan+myIxb/yPyIVnQHHxtqjEOHkRe2sf6suIAOAhpWwKvw6sjaluvGB9US4f3 dfLaOg8csSvI7cWRF7VQ==
MIME-Version: 1.0
Received: by 10.100.136.7 with SMTP id j7mr3756772and.64.1287036051040; Wed, 13 Oct 2010 23:00:51 -0700 (PDT)
Received: by 10.100.223.2 with HTTP; Wed, 13 Oct 2010 23:00:50 -0700 (PDT)
In-Reply-To: <AANLkTi=1wzU6ARvhf3XVP-ZK+rmRF5LAH-YzAYULg82m@mail.gmail.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> <FFDFD7371D517847AD71FBB08F9A3156254C4A752A@SP2-EX07VS06.ds.corp.yahoo.com> <90C41DD21FB7C64BB94121FBBC2E72343D4691FADB@P3PW5EX1MB01.EX1.SECURESERVER.NET> <AANLkTi=1wzU6ARvhf3XVP-ZK+rmRF5LAH-YzAYULg82m@mail.gmail.com>
Date: Wed, 13 Oct 2010 23:00:50 -0700
Message-ID: <AANLkTimsn_5DXd+cHZj+3BYoeVwOKAYCx92ze7Un1Vcm@mail.gmail.com>
From: John Panzer <jpanzer@google.com>
To: Breno <breno.demedeiros@gmail.com>
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable
X-System-Of-Record: true
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 06:02:05 -0000

In which case, nothing the legit server does can help that client.
Since they're talking to the evil.

On Wednesday, October 13, 2010, Breno <breno.demedeiros@gmail.com> wrote:
> Or a connection to evil will happen.
>
> On Wed, Oct 13, 2010 at 6:33 PM, Eran Hammer-Lahav <eran@hueniverse.com> wrote:
>> I don't think so. If you are not running a server on port 80, the connection will never happen and nothing bad will be send on the wire.
>>
>> EHL
>>
>>> -----Original Message-----
>>> From: oauth-bounces@ietf.org [mailto:oauth-bounces@ietf.org] On Behalf
>>> Of William Mills
>>> Sent: Wednesday, October 13, 2010 5:05 PM
>>> To: Breno; Jeff Lindsay
>>> Cc: oauth@ietf.org
>>> Subject: Re: [OAUTH-WG] Request sent to http: instead of https:`
>>>
>>> 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?
>>> _______________________________________________
>>> OAuth mailing list
>>> OAuth@ietf.org
>>> https://www.ietf.org/mailman/listinfo/oauth
>>
>
>
>
> --
> Breno de Medeiros
> _______________________________________________
> OAuth mailing list
> OAuth@ietf.org
> https://www.ietf.org/mailman/listinfo/oauth
>

-- 
--
John Panzer / Google
jpanzer@google.com / abstractioneer.org / @jpanzer

v2.23.0 | Report a Bug | By Email