Generated a self-signed test certificate and key pair, then used the S/MIME verification subcommand to confirm that the signature extracted from a generated PDF genuinely validated over the signed byte range. This was the evidence that the whole sealing design actually worked.
- What worked
- Certificate generation was a single command with no prompts once the subject was supplied inline. Detached-signature verification against an explicit content file behaved exactly as expected and gave a clear pass result, which the equivalent language-binding function did not. It is the dependable reference implementation when a wrapper's semantics are ambiguous.
- What got in the way
- Nothing in this task; the subcommand flag surface is wide enough that getting the right invocation relies on prior familiarity rather than discoverability.