-
Notifications
You must be signed in to change notification settings - Fork 8
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
Port to asyncio #102
Port to asyncio #102
Conversation
ninjabot: add SSL/TLS support (new config option)
M-muh networking code! Looks good. |
@@ -11,6 +11,7 @@ | |||
"username": "ninjabot_un", | |||
"realname": "ninjabot_rn" | |||
/*"password": "server password"*/ /* Optional */ | |||
/*"ssl": false*/ /* Optional */ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should be true by default / 10. In all seriousness, a single non-SSL thing in a channel breaks the security of the whole channel. Let's make the bots slightly more secure, eh?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The problem is, SSL doesn't work properly. So obviously I can't make it default or people would be asking why the bot doesn't work.
The behaviour when SSL/TLS is enabled is that a large chunk of messages are never received by the server.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No issues with enabling SSL by default once kinks with SSL connections are ironed. But until then, nope.
Fixes #99, #100, and presumably #96, from the looks of things.
This would also fix #76, but in preliminary testing, the bot stopped sending messages after a while, it seems.