Re: [ietf-privacy] [websec] HPKP and privacy

SM <sm@resistor.net> Wed, 10 July 2013 00:41 UTC

Message-Id: <6.2.5.6.2.20130709172646.0b2a0978@resistor.net>
Date: Tue, 09 Jul 2013 17:38:34 -0700
To: Tom Ritter <tom@ritter.vg>
From: SM <sm@resistor.net>
In-Reply-To: <CA+cU71nEPm95MLPAcgDjFdzuR5eLT98+-WEsxpfSbH+dHq81UA@mail.g mail.com>
References: <CAOe4UimnDeEU3BHwy5KrCOi=4KxLPRuuKZRHQv49s1_BNg44Ww@mail.gmail.com> <51C7F08F.2090205@gondrom.org> <CAOe4Ui=Teo77EG3r+gsfeAVsHoykOsG=2cV8xVkiw+3SNoUvrg@mail.gmail.com> <CA+cU71nEPm95MLPAcgDjFdzuR5eLT98+-WEsxpfSbH+dHq81UA@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Cc: ietf-privacy@ietf.org, Joseph Bonneau <jbonneau@gmail.com>, websec@ietf.org
Subject: Re: [ietf-privacy] [websec] HPKP and privacy
Precedence: list

Hi Tom,

[Cc to privacy-nuts :-)]

At 06:29 09-07-2013, Tom Ritter wrote:
>On 9 July 2013 00:23, Joseph Bonneau <jbonneau@gmail.com> wrote:
> > There is no advice to implementers, however. Is there a reason not to make
> > explicit that user agents SHOULD remove pins for privacy reasons, something
> > along the lines of the text I suggested previously:
>
>It states that UAs must let people clear data:
>
> >UAs MUST have a way for users to clear current pins for Pinned Hosts.
> >UAs SHOULD have a way for users to query the current state of Pinned
> >Hosts.

I read Section 5 and missed the above (it's in Section 7).  Section 5 
basically says that HPKP can be a super-cookie.  It then explains two 
attack scenarios.  I think that the privacy considerations should be 
made explicit.

Regards,
-sm

Re: [ietf-privacy] [websec] HPKP and privacy SM
Re: [ietf-privacy] [websec] HPKP and privacy Chris Palmer