Hi, I am trying to implement a client for NRTM server since RADb is supporting it. I have some confusion about the signing key.
The current draft says: "...If present, it MUST be an Ed25519 [RFC8032] public key encoded in base64 [RFC4648], which matches the private key the mirror server will start using to sign the Update Notification File in the near future. " However, in the example, the field "next_signing_key": "96..ae" looks like a byte representation instead of a base64 representation of a ed25519 public key. (Since the key length of a ed25519 public key is not a multiple of 3, the base64 representation must ends with a "=".) Please clarify! (I noticed it because I am using Go and it's conveniently using byte representation) Thanks! Shon Huang
_______________________________________________ GROW mailing list [email protected] https://www.ietf.org/mailman/listinfo/grow
