Skip to content
This repository has been archived by the owner on Nov 15, 2022. It is now read-only.

managing secrets for Kedge project #551

Open
4 tasks
kadel opened this issue Jan 2, 2018 · 0 comments
Open
4 tasks

managing secrets for Kedge project #551

kadel opened this issue Jan 2, 2018 · 0 comments

Comments

@kadel
Copy link
Member

kadel commented Jan 2, 2018

We have different secrets, bot accounts, and accounts for different services

We need a secure way to store secrets, so anyone who needs to use those can use it.

I have setup https://github.com/kadel/project, this is to verify that everything works properly.
My intention is to move it to github.com/kedgeproject/project once we all agree that this is OK.

So far I've added Charlies and Surajs keys.

Charlie: Charlie Drage [email protected] (C037D617) http://pgp.mit.edu/pks/lookup?op=vindex&search=0xDA227403C037D617
Suraj: Suraj Deshmukh [email protected] (3115815E) http://pgp.mit.edu/pks/lookup?op=vindex&search=0xC696ABB83115815E

Please verify that those keys are really yours.
After installing BlackBox you should verify that you have access to encrypted files running the following command:

blackbox_cat accounts.txt.gpg

It is just GPG encryption, you can read files without BlackBox using just gpg (gpg --decrypt accounts.txt.gpg).
BlackBox is there just to make key management easier.

@containscafeine and @pradeepto , please send me your public PGP keys so I can give you access to encrypted files.

Once verified that right people have access to it we should start adding passwords and secrets to it.

  • bintray api key and user
  • github.com/kedge-bot password
  • travis secrets $ecrypted_91569b511922_key $encrypted_91569b511922_iv
  • deploy key used for docs and for json schema
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant