#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- draft/source/diff?spec=svnfc4bef2ce138d467182832a362831b6d63ea9cdc&r=fc4bef2ce138d467182832a362831b6d63ea9cdc&format=side&path =/draft-ietf-websec-key-pinning.xml -- -------------------------------+-------------------------------- Reporter: pal...@google.com | Owner: pal...@google.com Type: defect | Status: closed Priority: major | Milestone: Component: key-pinning | Version: Severity: - | Resolution: fixed Keywords: | -------------------------------+-------------------------------- Ticket URL: <http://trac.tools.ietf.org/wg/websec/trac/ticket/55#comment:3> websec <http://tools.ietf.org/websec/> _______________________________________________ websec mailing list websec@ietf.org https://www.ietf.org/mailman/listinfo/websec
