IETF Logo Mail Archive

Re: [OAUTH-WG] Understanding how OpenSocial uses OAuth 1.0a

Brian Eaton <beaton@google.com> Fri, 19 March 2010 18:45 UTC

Return-Path: <beaton@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 47F093A67A1 for <oauth@core3.amsl.com>; Fri, 19 Mar 2010 11:45:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.412
X-Spam-Level:
X-Spam-Status: No, score=-101.412 tagged_above=-999 required=5 tests=[AWL=-0.565, BAYES_00=-2.599, DNS_FROM_OPENWHOIS=1.13, FM_FORGED_GMAIL=0.622, 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 PVUNrQpLQsZl for <oauth@core3.amsl.com>; Fri, 19 Mar 2010 11:45:47 -0700 (PDT)
Received: from smtp-out.google.com (smtp-out.google.com [74.125.121.35]) by core3.amsl.com (Postfix) with ESMTP id 696CF3A67EC for <oauth@ietf.org>; Fri, 19 Mar 2010 11:45:47 -0700 (PDT)
Received: from kpbe20.cbf.corp.google.com (kpbe20.cbf.corp.google.com [172.25.105.84]) by smtp-out.google.com with ESMTP id o2JIjrg5029681 for <oauth@ietf.org>; Fri, 19 Mar 2010 19:45:57 +0100
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=google.com; s=beta; t=1269024357; bh=Ed/Zfx4TgOxWIpId/zmsGSXfpGQ=; h=MIME-Version:In-Reply-To:References:Date:Message-ID:Subject:From: To:Cc:Content-Type; b=h4Fhq3Git8DJfvxNu36Emf55aB6e3bQItdu/RqTQCik1pYBMcZ4R8eJuLhxwFo9oj QQlWY+no1FYpx2xvXaHyw==
DomainKey-Signature: a=rsa-sha1; s=beta; d=google.com; c=nofws; q=dns; h=mime-version:in-reply-to:references:date:message-id:subject:from:to: cc:content-type:x-system-of-record; b=uiC18CtKok5RN4M85Uc6rz0DBuYHipfx7W20yrj3qTfb480tXChInpmszO7+kEp+D 2gweT0T1i8UaMH0bsrsYA==
Received: from vws18 (vws18.prod.google.com [10.241.21.146]) by kpbe20.cbf.corp.google.com with ESMTP id o2JIjoxU005384 for <oauth@ietf.org>; Fri, 19 Mar 2010 11:45:51 -0700
Received: by vws18 with SMTP id 18so567455vws.20 for <oauth@ietf.org>; Fri, 19 Mar 2010 11:45:50 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.220.122.210 with SMTP id m18mr213671vcr.94.1269024350451; Fri, 19 Mar 2010 11:45:50 -0700 (PDT)
In-Reply-To: <daf5b9571003191144j74ea597cgf06ef3ba449cecef@mail.gmail.com>
References: <fd6741651003161112y2eceb494ue28db2644ba1d32a@mail.gmail.com> <68f4a0e81003191052m7ab778d6n330e58bd58b9f924@mail.gmail.com> <daf5b9571003191144j74ea597cgf06ef3ba449cecef@mail.gmail.com>
Date: Fri, 19 Mar 2010 11:45:50 -0700
Message-ID: <daf5b9571003191145v5ee86c9bw324ceb9366f1c6bb@mail.gmail.com>
From: Brian Eaton <beaton@google.com>
To: Ethan Jewett <esjewett@gmail.com>
Content-Type: text/plain; charset="ISO-8859-1"
X-System-Of-Record: true
Cc: OAuth WG <oauth@ietf.org>
Subject: Re: [OAUTH-WG] Understanding how OpenSocial uses OAuth 1.0a
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: Fri, 19 Mar 2010 18:45:48 -0000

On Fri, Mar 19, 2010 at 11:44 AM, Brian Eaton <beaton@google.com> wrote:
> Plaintext doesn't work in this context, because it sends long-lived
> secrets in clear-text to servers that are under the control of the
> application author, or, in the case of gadgets, everyone viewing the
> gadget.

Ah, the other reason plaintext doesn't work is because one of the
goals is to guarantee the integrity of the identity information passed
in the request - neither the application author nor the viewer of the
application is permitted to tamper with those parameters.

v2.23.0 | Report a Bug | By Email