W3C home > Mailing lists > Public > ietf-http-wg@w3.org > October to December 2013

Re: SECDIR review of draft-ietf-httpbis-p7-auth-24

From: Julian Reschke <julian.reschke@gmx.de>
Date: Wed, 30 Oct 2013 14:40:42 +0100
Message-ID: <52710C5A.9040705@gmx.de>
To: Stephen Kent <kent@bbn.com>, secdir <secdir@ietf.org>, fielding@gbiv.com, mnot@pobox.com, Barry Leiba <barryleiba@computer.org>, Pete Resnick <presnick@qti.qualcomm.com>, "Mankin, Allison" <amankin@verisign.com>, HTTP Working Group <ietf-http-wg@w3.org>
Stephen,

On 2013-10-29 20:35, Stephen Kent wrote:
> ...
> The Security Considerations section (6) is about one page in length. It
> references the SC sections in two in I-Ds:
> draft-ietf-httpbis-p1-messaging-24 and
> draft-ietf-httpbis-p2-semantics-24. Both of these I-Ds have non-trivial
> SC sections, but one cannot say that this document has an acceptable SC
> section until those documents are finalized. They are both normative
> references, so this doc will nor progress independently, but there will
> still be a need to revisit this SC when those SCs are finalized.

These two other documents are in IETF LC as well.

> The SC section here addresses only two issues: purging credentials in
> clients and user agents, and protection spaces. The discussion of the
> former topic does not discuss how credential purging applies to proxies.

As per httpbis-p1, a proxy is a client as well ('An HTTP "client" is a 
program that establishes a connection to a server for the purpose of 
sending one or more HTTP requests.' -- 
<http://greenbytes.de/tech/webdav/draft-ietf-httpbis-p1-messaging-24.html#rfc.section.2.1>). 
Does this address your comment?

> Also, it is not clear that a user control for credential purging will
> have the desired effect given a potentially complex GUI environment. The

Any proposal for enhancing the text?

> discussion of protection spaces provides useful suggestions on how to
> minimize credential exposure.
>
> I was a bit surprised that there was no advice deprecating the use of
> passwords as credentials, if only to make a statement on this topic.

This document just defines the HTTP authentication framework. It's not 
intended to give general guidelines about the security of new 
authentication schemes. But then, if you have some concrete proposal for 
additional text, we're all ears.

Best regards, Julian
Received on Wednesday, 30 October 2013 13:41:21 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 1 March 2016 11:11:18 UTC