I'm trying to build a PKI for document signing but only using 2nd party auth and no client persistence.

I'm assuming I'd need to use something like a SCrypt key of the user credentials for the user's keys, and then at every use regenerate it and also renew a certificate for the user if it doesn't have a current one.

I'm not sure if I'm reasoning about it correctly, especially since I realized the way I previously envisioned it was wrong.

Doing it this way, wouldn't it make it possible to also sign data on offline machines (at least as well as any offline data modification where conflicts can occur)?


Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.