#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-
The text works for me.
On Mar 27, 2013, at 6:54 PM, websec issue tracker
trac+web...@grenache.tools.ietf.org
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
#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-
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
#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
