2 ms·
Right, what path would have led you to that doc page. I read a lot of doc pages and none of the paths I followed led to that one.
by timbray 5y ago
Right, what path would have led you to that doc page. I read a lot of doc pages and none of the paths I followed led to that one.
- nabla9 5y agoJust one click away. Go to https://golang.org/ https://golang.org/ click [Packages] Scroll down until you see crypto packages. Now you should see package named pkix and description of the package: pkix - contains shared, low level structures used for ASN.1 parsing and serialization of X.509 certificates, CRL and OCSP.
- timbray 5y agoCall me weird, but I tend to start by searching for what I think I'm looking for. I was looking for "serialize 25519" or something like that. None of "pkix", "ASN.1", "CRL", X.509, o "OCSP" were in my vocabulary when I started.
- nabla9 5y agoI see. 1. You needed to learn how the cryptographic serialization happens in practice. Including terminology. 2. You forgot to look again after you had learned all you needed to learn and wrote your own. It's easy to wander from learning to coding.
- NovemberWhiskey 5y agoI think the problem you had is basically that's in uncommon to be distributing bare public keys in the most common cryptography contexts. Public keys are nearly always part of certificates. I looked at the @bluesky identity post, and it seems to me that what's being described in the granting process is very close to a self-signed certificate. To link two identities, couldn't you create a self-signed certificate with two SANs that identify your identity on P1 and P2 and post the same certificate to both of them, then send links to the two posts to the ledger? An X.509 certificate is already a structured method to create a payload consisting of a public key, various claims as to identity of the subject, and a wrapping signature.