[Coder-Com] sugestion.. to avoid mass dcc exploit...
Hi, We're still getting some drones in Brazillian channels trying to exploit the DCC bug of mIRC.. would it be possible to create a channel mode for NOT allowing ctcp/dcc msgs to channels?? Some servers that derivated from bahamutt already do that.. like the brasnet.org servers... Thanx, Mario Meyer (DJMario @ undernet)
Re: [Coder-Com] sugestion.. to avoid mass dcc exploit...
Sunday, November 16, 2003, 7:52:06 PM, you wrote: ML> We're still getting some drones in Brazillian channels trying to exploit the ML> DCC bug of mIRC.. would it be possible to create a channel mode for NOT ML> allowing ctcp/dcc msgs to channels?? Some servers that derivated from ML> bahamutt already do that.. like the brasnet.org servers... I suggest you take a look at: http://cvs.quakenet.org/cgi-bin/cvsweb.cgi/asuka/patches/asuka-cC.patch?rev=1.9&content-type=text/x-cvsweb-markup Regards, Ian Packer
Re: [Coder-Com] sugestion.. to avoid mass dcc exploit...
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ian Packer wrote:
| Sunday, November 16, 2003, 7:52:06 PM, you wrote:
|
| ML> We're still getting some drones in Brazillian channels trying to
exploit the
| ML> DCC bug of mIRC.. would it be possible to create a channel mode
for NOT
| ML> allowing ctcp/dcc msgs to channels?? Some servers that derivated from
| ML> bahamutt already do that.. like the brasnet.org servers...
|
| I suggest you take a look at:
|
http://cvs.quakenet.org/cgi-bin/cvsweb.cgi/asuka/patches/asuka-cC.patch?rev=1.9&content-type=text/x-cvsweb-markup
|
| Regards,
| Ian Packer
|
|
+ if ((chptr->mode.mode & MODE_NOCTCP) && ircd_strncmp(text,"\001ACTION
",8))
+for (ch=text;*ch;)
+ if (*ch++==1) {
+send_reply(sptr, ERR_CANNOTSENDTOCHAN, chptr->chname);
+return;
+ }
Uhm, can't I still do:
PRIVMSG #chan :\001ACTION is broken\001\001VERSION\001
Jeff
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.1 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQE/t+ZXGi4Ni4h3f1YRAsWaAJ9JP3AiSlwJtRZ8LTB71GA638VRpgCfR0xA
1/Egv++9/ZeMEjxEurNjKh4=
=fjTP
-END PGP SIGNATURE-
Re: [Coder-Com] sugestion.. to avoid mass dcc exploit...
On Sun, 2003-11-16 at 13:04, Jeff Fisher wrote:
> + if ((chptr->mode.mode & MODE_NOCTCP) && ircd_strncmp(text,"\001ACTION
> ",8))
> +for (ch=text;*ch;)
> + if (*ch++==1) {
> +send_reply(sptr, ERR_CANNOTSENDTOCHAN, chptr->chname);
> +return;
> + }
>
> Uhm, can't I still do:
>
> PRIVMSG #chan :\001ACTION is broken\001\001VERSION\001
>
> Jeff
most clients don't (or at least aren't supposed to) support that..
if you wanted, you could filter specifically for DCC sending to
channels; that's how bahamut does it.
//akl
Re: [Coder-Com] sugestion.. to avoid mass dcc exploit...
On 2003-11-16T14:34-0800, akl wrote: ) On Sun, 2003-11-16 at 13:04, Jeff Fisher wrote: ) > PRIVMSG #chan :\001ACTION is broken\001\001VERSION\001 ) most clients don't (or at least aren't supposed to) support that.. In my experience, most clients do support that. In any event, they are definitely "supposed to". CTCP messages are allowed to be embedded in normal messages, and are furthermore allowed to be stacked. http://www.irchelp.org/irchelp/rfc/ctcpspec.html ... - --- Example 3 - If the user actor wants to query the USERINFO of user victim, and is in the middle of a conversation, the client may decide to tack on USERINFO request on the end of a normal text message. Let's say actor wants to send the textmessage "Say hi to Ron\n\t/actor" and the CTCP request "USERINFO" to victim: PRIVMSG victim :Say hi to Ron\n\t/actor plus: USERINFO which after CTCP quoting become: PRIVMSG victim :Say hi to Ron\n\t/actor plus: USERINFO which gets merged into: PRIVMSG victim :Say hi to Ron\n\t/actor\001USERINFO\001 and after low level quoting: PRIVMSG victim :Say hi to Ron\020n\t/actor\001USERINFO\001 and sent off to the server. On victim's side, the message: :actor PRIVMSG victim :Say hi to Ron\020n\t/actor\001USERINFO\001 arrives. This gets low level dequoted into: :actor PRIVMSG victim :Say hi to Ron\n\t/actor\001USERINFO\001 and thereafter split up into: :actor PRIVMSG victim :Say hi to Ron\n\t/actor plus: USERINFO After CTCP dequoting both, the message: :actor PRIVMSG victim :Say hi to Ron\n\t/actor gets displayed, while the CTCP command: USERINFO gets replied to. -- Daniel Reed <[EMAIL PROTECTED]> http://naim-users.org/nmlorg/ http://naim.n.ml.org/ It is so easy to miss pretty trivial solutions to problems deemed complicated. The goal of a scientist is to find an interesting problem, and live off it for a while. The goal of an engineer is to evade interesting problems :) -- Vadim Antonov <[EMAIL PROTECTED]> on NANOG
Re: [Coder-Com] sugestion.. to avoid mass dcc exploit...
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 | | most clients don't (or at least aren't supposed to) support that.. either way -- this patch is broken. I won't get into the "supposed to" since Daniel did. Jeff -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.1 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQE/uEpdGi4Ni4h3f1YRAlB+AJ9j/ljjQiunspW/1wUuMPZQ3EcIrQCfZMQA uAQr/3I760Tuw3SsVr5fVv0= =VdZb -END PGP SIGNATURE-
Re: [Coder-Com] sugestion.. to avoid mass dcc exploit...
On Sun, 2003-11-16 at 16:04, Jeff Fisher wrote: > Uhm, can't I still do: > > PRIVMSG #chan :\001ACTION is broken\001\001VERSION\001 Congratulations; you have just discovered one of the many reasons servers should not parse PRIVMSG to filter out CTCP. -- Kevin L. Mitchell <[EMAIL PROTECTED]> signature.asc Description: This is a digitally signed message part
