The text works for me. On Mar 27, 2013, at 6:54 PM, websec issue tracker <[email protected]> wrote:
> #55: Clarify that the newest pinning information takes precedence > > > Comment (by [email protected]): > > 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=svn4f697cf66f747c18a5389922f484d9a1dbe85968&r=83bad3527ede8bb6ef52a8c220990ccd8762d9e7&format=side&path > =/draft-ietf-websec-key-pinning.xml > > -- > -------------------------------+-------------------------------- > Reporter: [email protected] | Owner: [email protected] > Type: defect | Status: assigned > Priority: major | Milestone: > Component: key-pinning | Version: > Severity: - | Resolution: > Keywords: | > -------------------------------+-------------------------------- > > Ticket URL: <http://trac.tools.ietf.org/wg/websec/trac/ticket/55#comment:2> > websec <http://tools.ietf.org/websec/> > > _______________________________________________ > websec mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/websec _______________________________________________ websec mailing list [email protected] https://www.ietf.org/mailman/listinfo/websec
