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

Added secure option to use a secure port other than 6697 #162

Merged
merged 4 commits into from Nov 13, 2011

Conversation

andresilva
Copy link
Contributor

No description provided.

@@ -34,6 +34,7 @@ class IrcBot extends Robot.Adapter
server: process.env.HUBOT_IRC_SERVER
password: process.env.HUBOT_IRC_PASSWORD
nickpass: process.env.HUBOT_IRC_NICKSERV_PASSWORD
secure: process.env.HUBOR_IRC_SECURE or false
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can we call this HUBOT_IRC_SSL_PORT or something similar instead?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That might lead people to think that it's supposed to be a port instead of a boolean, don't you think?

Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Personally I like HUBOT_IRC_SECURE as it maps to the option in node-irc.

@andresilva
Copy link
Contributor Author

Damn, I was doing some hacking on the repo and I din't realize it would show up on the pull request.

@tombell
Copy link
Contributor

tombell commented Nov 13, 2011

Fixed in #175.

@tombell tombell closed this Nov 13, 2011
…ash-with-alias

Add --alias (--enable-slash is deprecated)
@andresilva
Copy link
Contributor Author

It's not fixed.

  •  secure: if options.port is "6697" and options.usessl then true else false,
    

What if I want to use an ssl connection on a port other than 6697? That "and" should have been an "or".

Also, statements like this:

  • unflood: process.env.HUBOT_IRC_UNFLOOD or false

don't work as expected (or at least I wasn't able to make them work). If I set the environment variable to the value True, the string "True" will be compared to false. Any non-empty string is evaluated to true, therefore the string "True" will be sent to the irc constructor which was expecting a boolean, and the option will be ignored. The !! operator should be used instead to assert that the env variable was set.

Please correct me if I'm wrong.

Add support for host/port configuration in the XMPP adapter.
@tombell tombell reopened this Nov 13, 2011
@tombell
Copy link
Contributor

tombell commented Nov 13, 2011

Can you update this pull to fix those issues, then I'll merge it in?

…any guesses as to whether the port is secure or not.
@andresilva
Copy link
Contributor Author

Done.

@tombell
Copy link
Contributor

tombell commented Nov 13, 2011

Cool nice one. :)

tombell pushed a commit that referenced this pull request Nov 13, 2011
Added secure option to use a secure port other than 6697
@tombell tombell merged commit e7b7f11 into hubotio:master Nov 13, 2011
glucero pushed a commit to ProCern/hubot that referenced this pull request Aug 20, 2012
Added secure option to use a secure port other than 6697
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants