Re: OID encoding help
Robert Moskowitz <[email protected]> Sun, 7 May 2023 20:33:25 -0400
| Newsgroups | gmane.ietf.x509 |
|---|---|
| Message-ID | <[email protected]> |
On 5/7/23 17:53, Peter Gutmann wrote: > Robert Moskowitz <[email protected]> writes: > >> Per my number above, shouldn't the last 3 bytes be 02 06 06 ? > Ah, yeah, sorry, mistyped it. > >> Do I just concatinate these? Or does the Endorsement need a length byte of >> 7E in front of it? > It depends on what the ASN.1 definition for it is, is it the usual type-and- > value form? With Russ' help, I believe it is all sorted now. Then I had to work out how to get the base64 encoding needed for the CERT RR. I believe that is all set. I am really a hack at coding. I do so little of it. My serious joke is I never coded in 'C', only in 'B' (the Waterloo B compiler for Honeywell minis and mainframes back in the mid-80s). And Python is really challenging in how it handles variable types. Particularly if you hack at it as seldom as I. My scripts are at: https://github.com/ietf-wg-drip/drip-scripts and it is the endorse.py that makes the CERT RR. Now to actually lay out the DNS structure for allowing full testing of DRIP. I worked out some things late last week, and am now defining what I am calling the DRIP DKI (DRIP Key Infrastructure). Follow my stumbling along on the DRIP wg list. Bob _______________________________________________ pkix mailing list [email protected] https://www.ietf.org/mailman/listinfo/pkix