howdy all,
after some more quite programing, i have found out how some nasty ppl are detroying hubs for
useless reasons with new hub flooders.
it involves flooding a fake ip and port in the connecttome string to target and hopefully crash
the targeted address.
now this is very fullon, and actually puts the end users doing the attacking themselfs, but if everyone
running a server has a very strict script handling the ip address's being sent in the connectmeto
strings:- it can be harder to achieve a full flood of connections to attack a hub.
noza
wel my firend matt you sohuld try see plops antiflood
it is doing exactly what you said and protect the hub =)
QuoteOriginally posted by LiqUiD~TrolL
wel my firend matt you sohuld try see plops antiflood
it is doing exactly what you said and protect the hub =)
yep and it's also the feature i get the most complains about.
ppl seem 2 think this is a bug or a useless piece of protection.
users complain that they don't do anything wrong and ignore the msg deflood sends out.
but nomather how many complains i get i won't ever remove this protection from deflood.
on deflood 4 some ppl have disabled it themselfs, on version 5 they can't.
plop
heehhehe m8 well i thought the same thing when i saw it
but now i know =)
people who the don t know
they say ifyou don t then don t talk hahaha
good work plop ;-)
QuoteOriginally posted by LiqUiD~TrolL
wel my firend matt you sohuld try see plops antiflood
it is doing exactly what you said and protect the hub =)
thats good, aswell as all my scripts protect from this, but then comes the question-what about a proxy user!?!
neways...
real downloads of ptokax are uselless against this attack because a side script cant handle anything that their not allowed to, and ptokax allows the connection to fill the ports and doesnt disconnect flooding users :/
something smart to do is when a flood detection is detected, u simply close ur listening port to stop connections from filling up ur ports.
nough said