[eggheads-patches] PATCH1.8: eggdropCTCPServerReply.patch

George Van Osterom george.vo at alum.rpi.edu
Sat Mar 7 22:11:22 CST 2015


A user had a unique situation where a server was sending CTCP requests to
eggdrop. While it was determined in discussion there was no particular need
to have eggdrop reply to a server CTCP (because it just feels dirty), the
code does contain a bug where if the uhost sent is not in a standard
nick!ident at hostname.com <mailto:nick!ident at hostname.com>  format (like a
server would appear in the format "I.am.a.server"), it uses "" as the CTCP
reply nick, and the code ends up using the intended reply string as the
nickname

 

In this case, user!foo at bar.com <mailto:user!foo at bar.com>  versioned the bot,
this is what it sends back:

[h->] NOTICE user :VERSION eggdrop v1.8.0+preinit

 

Now, the server I.Am.A.Server versions the bot:

[h->] NOTICE  :VERSION eggdrop v1.8.0+preinit

 

Alas, no user! 

 

This patch checks to see if a nick is extracted from the hostmask that sent
the CTCP request and, if not, uses the entire hostmask as the reply
destination. 

 

 

-------------- next part --------------
A non-text attachment was scrubbed...
Name: eggdropCTCPServerReply.patch
Type: application/octet-stream
Size: 524 bytes
Desc: not available
URL: <http://lists.eggheads.org/pipermail/patches/attachments/20150307/4f077af6/attachment.obj>


More information about the Patches mailing list