#55: Clarify that the newest pinning information takes precedence
Changes (by pal...@google.com):
* status: assigned => closed
* resolution: => fixed
Comment:
Per discussion on the list, adopted Sleevi's text but changed "evict" to
"ignore".
https://code.google.com/p/key-pinning-
dr
On Mon, April 1, 2013 3:28 pm, Chris Palmer wrote:
> On Wed, Mar 27, 2013 at 7:54 PM, Tom Ritter wrote:
>
> > " The UA MUST evict all expired Known Pinned Hosts if at any time, an
> > expired Known Pinned Host exists in the cache"
> >
> > I use rrdtool to keep 5 years of statistics for my server.
On Wed, Mar 27, 2013 at 7:54 PM, Tom Ritter wrote:
> " The UA MUST evict all expired Known Pinned Hosts if at any time, an
> expired Known Pinned Host exists in the cache"
>
> I use rrdtool to keep 5 years of statistics for my server. Once, I
> accidentally set the date forward, to 2038, wiping
The text works for me.
On Mar 27, 2013, at 6:54 PM, websec issue tracker
wrote:
> #55: Clarify that the newest pinning information takes precedence
>
>
> Comment (by pal...@google.com):
>
> Ryan Sleevi has added text to the working copy that I believe resolves
> this ticket. Comments?
>
>
" The UA MUST evict all expired Known Pinned Hosts if at any time, an
expired Known Pinned Host exists in the cache"
I use rrdtool to keep 5 years of statistics for my server. Once, I
accidentally set the date forward, to 2038, wiping out my statistics -
there was no way to recover, because rrdto
#55: Clarify that the newest pinning information takes precedence
Comment (by pal...@google.com):
Ryan Sleevi has added text to the working copy that I believe resolves
this ticket. Comments?
https://code.google.com/p/key-pinning-
draft/source/diff?spec=svn4f697cf66f747c18a5389922f484d9a1d
Any thoughts on this text?
On Fri, Oct 19, 2012 at 2:33 PM, websec issue tracker
wrote:
> #55: Clarify that the newest pinning information takes precedence
>
> In section "Interactions With Preloaded Pin Lists", we need to specify
> that the newest information, even "stop pinning", must take p
#55: Clarify that the newest pinning information takes precedence
Changes (by palmer@…):
* status: new => assigned
--
-+---
Reporter: palmer@… | Owner: palmer@…
Type: defect | Status: assigned
Priority: major
