Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Encryption, take 5 #227

Merged
merged 4 commits into from
May 25, 2017
Merged

Encryption, take 5 #227

merged 4 commits into from
May 25, 2017

Conversation

KamilaBorowska
Copy link
Contributor

Okay, I hope this passes, with all the issues that happened before.

Essentially, this adds asymmetric encryption for hiding stuff like API keys in plain sight.

@KamilaBorowska
Copy link
Contributor Author

To explain how does it work:

The public key is uploaded on web server, and is accessible by everyone. Private key on the other hand is only on bot's side, and only chaos can decrypt messages encrypted with it.

@chaosbot
Copy link
Collaborator

🙆‍♀️ PR passed with a vote of 6 for and 0 against, with a weighted total of 6.0 and a threshold of 3.7.

See merge-commit d9d1c77 for more details.

@chaosbot chaosbot merged commit d9d1c77 into Chaosthebot:master May 25, 2017
chaosbot added a commit that referenced this pull request May 25, 2017
amoffat added a commit to amoffat/Chaos that referenced this pull request May 25, 2017
@sorcio caught reqs that don't need to be there, like flask and its deps.  some
of the new reqs there now are actually deps from the cryptography package that
weren't there from Chaosthebot#227
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants