Sharing Trust Policy between Crypto Libraries
stefw at redhat.com
Thu Dec 20 09:38:09 PST 2012
As many of you know, I've been working on a standard representation for
sharing trust policy between crypto libraries.
As it turns out the previous effort, called trust assertions 
suffered from several limitations, which no doubt many of you
recognized. I've since retired that concept .
After a bunch of discussion and thought, I've put together what I feel
is a representation of trust policy that is viable.
At its core it has the concept of "Stapled Certificate Extensions".
Basically: storing additional certificate extensions locally together
with a certificate anchor in order to constrain how it's used.
This document (which is a pretty early state) should explain more of how
that works, and the rationale behind it:
The bonus is, that this meshes perfectly into current certificate
validation algorithms, is extensible, but at the same time pretty easy
to implement or retrofit.
Any time spent on looking this concept over, commenting, pointing out
holes, etc. is super appreciated.
 Here's why:
More information about the p11-glue