-
Notifications
You must be signed in to change notification settings - Fork 170
Encryption #37
Comments
After some talk this is what the current idea would look like: When installing a plugin, currently it is assumed no variables need to be set. The diff --git a/zazu.json b/zazu.json
index 6d190ad..b5d212d 100644
--- a/zazu.json
+++ b/zazu.json
@@ -1,6 +1,9 @@
{
"name": "Gist",
"icon": "icon.png",
+ "variables": {
+ "token": "string.secure"
+ },
"blocks": {
"input": [
{ We can also allow the user to specify an "encryption driver", which would default to one we create like When Zazu loads it'll search the plugin config for "secure" keys and overwrite them in memory. For example: {
"name": "afaur/zazu-gist",
"variables": {
"token": {
"secure": "7f46165474d11ee5836777d85df2cdab"
}
}
} Would replace So the workflow would look like this:
When you open up Zazu with the new config:
AssumptionsWe assume the driver will ALWAYS need a password. What if you never wanted to share this file, but you wanted it to be secure. There could just be a driver that uses some randomly generated file as your password. The cc @tinytacoteam/zazu-core |
Storing an api key in your
zazurc.js
file means it can't be backed up to github or other public type places. There should be a way to easily add encrypted data to this file. Possibly related to the package manager #32The text was updated successfully, but these errors were encountered: