[OAUTH-WG] Username and Password flow: no captcha?

Andrew Arnott <andrewarnott@gmail.com> Mon, 07 June 2010 17:19 UTC

Return-Path: <andrewarnott@gmail.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 E3DEB3A6DD5 for <oauth@core3.amsl.com>; Mon, 7 Jun 2010 10:19:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.298
X-Spam-Level:
X-Spam-Status: No, score=-1.298 tagged_above=-999 required=5 tests=[AWL=1.300, BAYES_00=-2.599, HTML_MESSAGE=0.001]
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 OYQ2ZZkPsdfA for <oauth@core3.amsl.com>; Mon, 7 Jun 2010 10:19:00 -0700 (PDT)
Received: from mail-yw0-f171.google.com (mail-yw0-f171.google.com [209.85.211.171]) by core3.amsl.com (Postfix) with ESMTP id D858128C1F9 for <oauth@ietf.org>; Mon, 7 Jun 2010 08:41:07 -0700 (PDT)
Received: by ywh1 with SMTP id 1so2932284ywh.22 for <oauth@ietf.org>; Mon, 07 Jun 2010 08:41:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:mime-version:received:in-reply-to :references:from:date:message-id:subject:to:content-type; bh=a3mEIb7N0VJYghOfcZ5QoIWLl4Rq9AnA6tm9z0jj6ZI=; b=UChxehhDSox32HGlOBbEGsBH6OQc/Vq1bO7W7CoFGkkoZAeFPipuFtb7MYl1P7V9v/ PTv+aLRcwaDuu4QxyJr0A7DeClPexp8Qe6G5d7JL8s3Tg8ZXk/Js0uDShDk2doaFbltZ qUOFusbzorT8ozD0/E+GQjDgaKwH4cOk5G47c=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type; b=pk7PZCTH+w3nb7nE7GEkwT78F7Lc4DsJ52wj26vZfnvdJAe3b1f5lWVj/0cVmyCt1R oKCb95Hl6TUsSdQkfYTwG3FJM0jgSxalt0ROrm5QY459Mio86hQLIRukBpzwbnblhaFK VYsFsIRTfZD+gRU7QoBNM/ZNMsiaxRqRbH0FI=
Received: by 10.151.18.38 with SMTP id v38mr13917384ybi.420.1275925263289; Mon, 07 Jun 2010 08:41:03 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.151.26.19 with HTTP; Mon, 7 Jun 2010 08:40:42 -0700 (PDT)
In-Reply-To: <AANLkTint78W8GC5Jctc0je5dsmuY-Ket2aqI00tjl-NC@mail.gmail.com>
References: <AANLkTint78W8GC5Jctc0je5dsmuY-Ket2aqI00tjl-NC@mail.gmail.com>
From: Andrew Arnott <andrewarnott@gmail.com>
Date: Mon, 07 Jun 2010 08:40:42 -0700
Message-ID: <AANLkTilXJM7rphv02DvFsmMgSdjO0twY1nVIPGwduC6m@mail.gmail.com>
To: "OAuth WG (oauth@ietf.org)" <oauth@ietf.org>
Content-Type: multipart/alternative; boundary="000e0cdf1970140fb2048872806d"
Subject: [OAUTH-WG] Username and Password flow: no captcha?
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: Mon, 07 Jun 2010 17:19:01 -0000

In WRAP, there was a CAPTCHA in this profile, but I don't see it in the
latest OAuth 2.0 draft.  Since I've already implemented the CAPTCHA stuff
from WRAP, I'll leave it there if the OAuth 2.0 is likely to pick it up, or
rip it out now if OAuth 2.0 decided it wasn't necessary.

Does anyone from the WG have something they can say on the subject?
--
Andrew Arnott
"I [may] not agree with what you have to say, but I'll defend to the death
your right to say it." - S. G. Tallentyre