Hi Steve: On 2010-11-16, at 3:53 PM, Dr. Stephen Henson wrote:
> On Tue, Nov 16, 2010, Patrick Patterson wrote: > >> That said, when I pipe the output through asn1parse, I don't see the SID >> information, so I'm not sure where the cms command would pull it from. >> > > It parses the structure and outputs the fields it receives in human readable > format. I took the output you posted to see the key ID. > > You wont see anything obvious in the output of asn1parse because the SID field > is implicitly tagged and in general there is no way to know how such a field > is interpreted. > > If you use asn1parse on the output you posted you'll see this: > > 594:d=5 hl=4 l= 257 prim: BIT STRING > 855:d=3 hl=2 l= 55 cons: SET > 857:d=4 hl=2 l= 53 cons: SEQUENCE > 859:d=5 hl=2 l= 1 prim: INTEGER :03 > 862:d=5 hl=2 l= 20 prim: cont [ 0 ] <--------- KID > 884:d=5 hl=2 l= 7 cons: SEQUENCE > 886:d=6 hl=2 l= 5 prim: OBJECT :sha1 > 893:d=5 hl=2 l= 0 cons: cont [ 0 ] > 895:d=5 hl=2 l= 13 cons: SEQUENCE > 897:d=6 hl=2 l= 9 prim: OBJECT :rsaEncryption > 908:d=6 hl=2 l= 0 prim: NULL > 910:d=5 hl=2 l= 0 prim: OCTET STRING > > The key ID is the line indicated. Ah - Ok - that explains it. Thanks for your help. --- Patrick Patterson Chief PKI Architect Carillon Information Security Inc. http://www.carillon.ca ______________________________________________________________________ OpenSSL Project http://www.openssl.org Development Mailing List [email protected] Automated List Manager [email protected]
