API use and documentation
See original GitHub issueIn a previous version of yopass there was a rudimental documentation of an API via HTTPS and JSON (see here).
Since your last bigger rewrite and the change to the sjcl cryptolibrary this part is missing in the README of the project.
We consider to automate a secure secret delivery in one of our internal services, so yopass would be a nice solution. (A yopass instance is already running but at this point only used in browser)
While the most of the JSON API is still working as expected…
# request
curl --header "Content-Type: application/json" \
--request POST \
--data '{"secret":"secret","Expiration":3600}' \
https://dasvcjfzrl.execute-api.eu-west-1.amazonaws.com/dev/secret
# response
{"message":"ea75ddc4-bcad-43b7-b767-7546253e8ca8"}
… At this point I need to know how the encryption part can be done locally without JS before sending the request to the server. You seem to use the SJCL defaults.
But I haven’t got this managed so far. Do you have an idea on how an api client can do that?
It would be nice to have this as an official feature back again.
Issue Analytics
- State:
- Created 5 years ago
- Comments:6 (1 by maintainers)
Top GitHub Comments
Hi. We have created a simple shell and node script to automate calls to Whisper encryption API through CLI. If someone needs it, we can share the code. Best regards.
In case folks try to get bahho’s version working on a mac (note curl doesn’t support OAuth, so if your site uses Google auth, it will complain about no javascript support - look at headless chrome or macedogm idea above that uses node):