W3C home > Mailing lists > Public > ietf-http-wg@w3.org > April to June 2012

Re: WGLC #348: Realms and scope

From: Martin Thomson <martin.thomson@gmail.com>
Date: Thu, 31 May 2012 09:11:45 -0700
Message-ID: <CABkgnnVyGh4AvakXTpMsoF5Ge8rEY69SHMvotS2StF+Pg3rYAA@mail.gmail.com>
To: Mark Nottingham <mnot@mnot.net>
Cc: HTTP Working Group <ietf-http-wg@w3.org>
On 31 May 2012 05:09, Mark Nottingham <mnot@mnot.net> wrote:
> 6.2 Protection Spaces
>
> Authentication schemes that use the "realm" mechanism for establishing a protection space will expose credentials to all resources on a server. This makes it possible for a resource to harvest authentication credentials for other resources on the same server.
>
> This is of particular concern when a servers hosts resources for multiple parties. Possible mitigation strategies include restricting direct access to authentication credentials (i.e., not making the content of the Authorization request header available), and separating protection spaces by using a different hostname for each party.

Thanks.  That addresses my concern.

Though it would seem that the problem isn't well understood.  Maybe
insert a bit more exposition...

"""[...] will expose credentials to all resources on a server. Clients
that have successfully made authenticated requests with a resource can
use the same authentication credentials for all resources on the same
server. This makes it possible for a [...]"""
Received on Thursday, 31 May 2012 16:12:20 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Thursday, 31 May 2012 16:12:28 GMT