On Thu, Aug 4, 2011 at 9:34 PM, Joe Hildebrand <[email protected]> wrote: > On 8/4/11 4:48 PM, "Hal Lockhart" <[email protected]> wrote: > >>> 3) A Standards Track document specifying how to encode public >>> keys as JSON-structured objects. >>> >> >> I would like to push back on the idea of only supporting naked public keys. >> It >> is my understanding that common cryto libraries, e.g. OpenSSL, expect public >> keys to be in certificates and the coding to get them to accept a naked key >> as >> input is ugly. I don't think they care if the cert is self signed or even >> signed at all, its just a format issue. > > Just doing the math yourself, from scratch, is pretty easy if you have the > bare key. It's nigh-on trivial if you have a bigint library. Solution: > don't use OpenSSL. I propose we don't get bogged down in the certificate > problem for the moment.
Cryptographer's warning: do not do this. Hard hat area ahead. -Ekr _______________________________________________ woes mailing list [email protected] https://www.ietf.org/mailman/listinfo/woes
