Any rfc-compliant server would not allow any user to hold the nick -telnet, as it does not start with a letter (psyBNC makes use of this aswell when communicating with the user). "-telnet"-hosts would'nt impose any major security issues by themselves, allowing anyone to telnet to it however would.Alchera wrote:Anyone with the nick -telnet gets recognised as the bot owner (nothing to do with telnet btw); no idea why this is added, maybe a hangover from the first eggdrop. I'd be removing it.
Most common practice of these would be if you wish to allow telnet-connections from additional hosts (such as localhost, 192.168.x.x that really would'nt make any sence on IRC), as upon any telnet connection, a identd-query is made, and the following hostmask is checked against the userlist: -telnet!<ident>@<host>. If the first match has +p, the connection is allowed (assuming require-p is set to 1, otherwize check for +o). Also, if no identd-service responds to the query, "telnet" is used in it's place (mIRC and a few other clients have a habit of only answering identd-queries while connecting to a server).
wether or not to have !*ident/!?ident/!~ident or !ident, that depends on how you set strict-host.
I do find it abit odd that you don't even get a dcc chat-request from your bot when you use /ctcp chat, yet /dcc chat works just fine.
