comparison with other stored security state mechanisms [was: Re: Sharing Trust Policy between Crypto Libraries]
Daniel Kahn Gillmor
dkg at fifthhorseman.net
Thu Jan 3 15:08:54 PST 2013
On 12/20/2012 12:38 PM, Stef Walter wrote:
In addition to the list of alternate extension mechanisms reviewed in
this document, It might be useful to compare chromium's internal
blacklist/security state mechanism:
This is related to (among other things) the "key pinning" concept
currently advanced in the websec working group:
(see also my recent e-mail on this list 'Different meanings of "Pinning"?').
Similarly to websec-key-pinning, HSTS and TACK are examples of per-peer
secure communications policy that would ideally be shared across
I don't think the current draft can support any of these mechanisms, and
perhaps they're out of scope; but maybe there are parts of them that
shouldn't be out of scope?
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 1027 bytes
Desc: OpenPGP digital signature
More information about the p11-glue