Anti ConnectToMe DDOS
 

News:

11 April 2017 - PtokaX 0.5.2.2 released...
8 April 2015 Anti child and anti pedo pr0n scripts are not allowed anymore on this board!
28 September 2015 - PtokaX 0.5.2.1 for Windows 10 IoT released...
3 September 2015 - PtokaX 0.5.2.1 released...
16 August 2015 - PtokaX 0.5.2.0 released...
1 August 2015 - Crowdfunding for ADC protocol support in PtokaX ended. Clearly nobody want ADC support...
30 June 2015 - PtokaX 0.5.1.0 released...
30 April 2015 Crowdfunding for ADC protocol support in PtokaX
26 April 2015 New support hub!
20 February 2015 - PtokaX 0.5.0.3 released...
13 April 2014 - PtokaX 0.5.0.2 released...
23 March 2014 - PtokaX testing version 0.5.0.1 build 454 is available.
04 March 2014 - PtokaX.org sites were temporary down because of DDOS attacks and issues with hosting service provider.

Main Menu

Anti ConnectToMe DDOS

Started by PPK, 17 January, 2015, 16:14:46

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

PPK

This script is sending reaction to $MyNick received from user. This is usually used as ddos when bad user or bad hubowner sending connection request ($ConnectToMe) with address of hub that he want to attack.
Script is very simple and support on client side is needed. Actually it is supported in FlylinkDC++

Code: lua
function UnknownArrival(tUser, sData) 
	if sData:sub(1, 8) == "$MyNick " then
		Core.SendToUser(tUser, "$Error CTM2HUB|")
		Core.Disconnect(tUser)
	end
end


How this works. Description as i'm received it from Rolex.

Quote
HUB1      = exploited hub that allows to send fake CTM
HUB2      = attacked hub
HUB2.ADDR   = address of attacked hub

DC1      = a bot that sends bad CTM requests to HUB1
DC2      = regular user on HUB1

DC1   ->   HUB1   $ConnectToMe DC2 HUB2.ADDR|
HUB1   ->   DC2   $ConnectToMe DC2 HUB2.ADDR|

DC2 doesnt find HUB2.ADDR in his blacklist and continues to process CTM request

DC2   ->   HUB2   socket_connect(HUB2.ADDR) + $MyNick DC2|$Lock ABC|
HUB2   ->   DC2   $Error CTM2HUB|      (this is the part needed to be done by the hub)

DC2 adds HUB2.ADDR  in his blacklist and closes connection

DC1   ->   HUB1   $ConnectToMe DC2 HUB2.ADDR|
HUB1   ->   DC2   $ConnectToMe DC2 HUB2.ADDR|

DC2 finds HUB2.ADDR in blacklist and ignores CTM request
"Most of you are familiar with the virtues of a programmer. There are three, of course: laziness, impatience, and hubris." - Larry Wall

SMF spam blocked by CleanTalk