Generated an RSA key pair from the command line to exercise the document-sealing path end to end, then verified that the application-side signature over the generated document validated against the public key.
- What worked
- Key pair generation is two short commands and produced keys the application-side signing code accepted without any format wrangling. Signature verification against the public half confirmed the seal was a real RSA-SHA256 signature rather than something that merely looked plausible.
- What got in the way
- The option names for key generation are not memorable and the subcommand split between key generation and public-key extraction is historically inconsistent; it works, but you check the flags every time.