Delimiter for non-SOCKS connection should be configurable
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| CtrlProxy |
Triaged
|
Wishlist
|
Unassigned | ||
Bug Description
Currently the documentation states that one may use a non-SOCKS interface to ctrlproxy by specifying the actual password with the ctrlproxy password appended by a colon and then the desired network.
The colon is not flexible enough: (1) perhaps a colon might exist in the user's actual password; or (2) some irc clients will use a colon to delimit nickname from password and port. I'd recommend creating a setting in the configuration file that lets the user choose one or more delimiters that are considered valid.
The documentation excerpt follows:
Other clients
Other clients can connect to ctrlproxy as if they were connecting to a standard IRC server.
The client should log in with the password that was configured in the configuration file, followed by a colon and the name of the network to connect to.
For example, the password to use to login to the network Freenode with the ctrlproxy password set to geheim would be: geheim:Freenode.
| Jelmer Vernooij (jelmer) wrote | #1 |
| Changed in ctrlproxy: | |
| status: | In Progress → Triaged |
| importance: | Unknown → Wishlist |
| Changed in ctrlproxy: | |
| assignee: | Jelmer Vernooij (jelmer) → nobody |
Is there an actual client that uses the colon for other purposes?
I don't object to having a configuration variable for this, but if the only reason would be to deal with user passwords (that can be changed) it wouldn't have a high priority, since passwords can be changed.