IETF Logo Mail Archive

Re: [apps-discuss] [http-auth] [saag] [websec] [kitten] HTTP authentication: the next generation

Tim <tim-research@sentinelchicken.org> Thu, 16 December 2010 20:47 UTC

Return-Path: <tim-research@sentinelchicken.org>
X-Original-To: apps-discuss@core3.amsl.com
Delivered-To: apps-discuss@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D5FE33A696C for <apps-discuss@core3.amsl.com>; Thu, 16 Dec 2010 12:47:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.932
X-Spam-Level:
X-Spam-Status: No, score=-1.932 tagged_above=-999 required=5 tests=[AWL=-0.267, BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, J_CHICKENPOX_46=0.6]
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 ITvMMO8btX4E for <apps-discuss@core3.amsl.com>; Thu, 16 Dec 2010 12:47:06 -0800 (PST)
Received: from sentinelchicken.org (mail.sentinelchicken.org [69.168.48.72]) by core3.amsl.com (Postfix) with ESMTP id 81B9E3A69CC for <apps-discuss@ietf.org>; Thu, 16 Dec 2010 12:47:06 -0800 (PST)
Received: (qmail 6686 invoked from network); 16 Dec 2010 20:58:24 -0000
Received: from unknown (HELO pascal.sentinelchicken.org) (10.81.64.2) by feynman.sentinelchicken.org with ESMTPS (DHE-RSA-AES256-SHA encrypted); 16 Dec 2010 20:58:24 -0000
Received: (qmail 17024 invoked from network); 16 Dec 2010 20:52:27 -0000
Received: from shannon.sentinelchicken.org (10.81.64.4) by pascal.sentinelchicken.org with SMTP; 16 Dec 2010 20:52:27 -0000
Received: (nullmailer pid 10758 invoked by uid 1000); Thu, 16 Dec 2010 20:48:49 -0000
Date: Thu, 16 Dec 2010 12:48:49 -0800
From: Tim <tim-research@sentinelchicken.org>
To: Marsh Ray <marsh@extendedsubset.com>
Message-ID: <20101216204849.GX5009@sentinelchicken.org>
References: <2229.1292235952.971571@puncture> <4D05FB8F.3070804@qbik.com> <2229.1292239384.281779@puncture> <96517E19-5DC7-47A0-8C21-C710F6F8F772@tzi.org> <5D5AF795-22AB-4726-B791-3706693466C3@checkpoint.com> <4D063CA5.8060907@gmail.com> <878FA115-D801-4063-AD87-DB2C2B2DE0D1@checkpoint.com> <4D0672F2.4070600@extendedsubset.com> <201012161827.NAA03511@Sparkle.Rodents-Montreal.ORG> <4D0A6969.7010309@extendedsubset.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <4D0A6969.7010309@extendedsubset.com>
User-Agent: Mutt/1.5.20 (2009-06-14)
X-Mailman-Approved-At: Fri, 17 Dec 2010 14:12:09 -0800
Cc: apps-discuss@ietf.org, websec@ietf.org, kitten@ietf.org, http-auth@ietf.org, der Mouse <mouse@Rodents-Montreal.ORG>, saag@ietf.org, ietf-http-wg@w3.org
Subject: Re: [apps-discuss] [http-auth] [saag] [websec] [kitten] HTTP authentication: the next generation
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: General discussion of application-layer protocols <apps-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/apps-discuss>
List-Post: <mailto:apps-discuss@ietf.org>
List-Help: <mailto:apps-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 Dec 2010 20:47:06 -0000

> Even still, how do you convince a web designer that they must give
> up their HTML login form for security when they have an HTML login
> form to choose the password in the first place?

This is a good point.  Something that may need to be considered in any
transition plan away from form+cookie auth.  

Should some HTTP Authentication mechanism to sign up for new accounts
and change passwords?

tim

v2.31.3 | Report a Bug | By Email | System Status