-
Notifications
You must be signed in to change notification settings - Fork 22
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
Allow joining password protected channels #64
Comments
This is a great RFE, but I'm not sure about the config syntax. Do you have any other suggestions? Will have to think about this. |
Are you unsure about the password being parsed correctly? Or do you not like the proposed delimiter characters? I can also imagine the following simple config syntaxes:
or
If you choose different delimiters you get more variations. Another solution would be to use a different file format like json which supports tree like struktures. |
One problem with using
So only
Using another parameter, |
Curious if anyone has made an update to support this feature? Still appears to be no way to allow a saxo bot so join a key/password protected IRC channel. Even with the 'join' command. |
Here is a patch that implement the channel,passwd. I had to change the behavior within irc.py to use ":" quickly going trough the RFC, i think this is not needed, not intended for client irc code (not double checked). passwd channel access didn't worked with "JOIN: #channel password" but does with "JOIN #channel password". All seems to work happily with this patch for us. |
I have looked at the documentation and I don't see a way to configure a password for a password protected irc channel. So I'd like to see this enhancement in saxo.
According to RFC1459, 4.2.3.1 Channel modes you can set a password protected channel like:
To solve this issue three things must be done imho:
I. configure password protected channels, for example
II. let saxo join a channel by passing the password, see Wiki IRC_Commands for the irc command. I think irc.py needs to be changed
III. update the documentation to show how the configuration is done, probably in config.md
Tell me what you think about this.
The text was updated successfully, but these errors were encountered: