[GitHub] [incubator-teaclave] ya0guang commented on issue #554: Generating key and signing a file

[GitBox <gi...@apache.org>]

ya0guang commented on issue #554:
URL: https://github.com/apache/incubator-teaclave/issues/554#issuecomment-931358162


   It seems the whole process is stateful, where "first run" generates a key pair and the key will be used in "following runs". In general, Teaclave cannot handle statefule tasks since FaaS is stateless in nature.
   
   However, specifically in your case, an alternative solution is like this:
   
   1. Prepare a function which outputs a key for signing, and this "key file" will be an encrypted output.
   2. Make your Python application accepting an additional input arg, the "key file" generated in step 1. This "key file" can be provided by another party (rather than the user, e.g. service provider), and the Python application sign PDF file with the corresponding key.
   
   If you really want to make it a single function, you can always ask the function to take another input to choose if it's going to generate a key or sign a PDF.
   
   Hope I understand your requirements correctly and hope this can help.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscribe@teaclave.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org



---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@teaclave.apache.org
For additional commands, e-mail: notifications-help@teaclave.apache.org