Dave Kemp wrote:
A single attribute containing a list of (issuerName, serialNumber,
hash(issuerPublicKey)) could serve the dual purpose of binding a normal
certificate into the transaction (to prevent spoofing) and to bind
selected attribute certs into the transaction (to prevent third parties
from inserting unwanted-but-valid attribute certs). I support the
definition of such an attribute, as discussed a while back in the
context of shared public keys.
It never occured to me to use the issuer's key.
The advantage of using Dave's method (issuer's key hash
along with issuer name and serial number) is that an Attribute Authority that
performs intensive issuing operations can cache this information if all base
certicates are issued by the same CA, where as the solution that I proposed
requires more CPU time since there is a calculation for each subject's public
key.
Now all we have to do is worry about dealing with multiple attribute
authorities. That can wait for another list :)
Capt Hayes