Handling Private/Public Key Generation, Storage, and Verification on the Server

Our system has three actor types: User, Service, and Package. Storing a separate public/private key pair for every Package is impractical. For Users, though, each account should have its own key pair (private key stored securely on the host, public key published in the actor document). I’m not certain of the exact storage design yet, but we should implement per-user key pairs. Remote users can be verified using their published public keys.