New on LowEndTalk? Please Register and read our Community Rules.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
This discussion has been closed.
Comments
"Didn't realize it would cause trouble for your node." Lmfao
"I am using a pay-per-hour provider for that" a booter?
So this is who has been hitting the rapidswitch hosts?
I doubt it. Slowloris is not a bandwidth-based attack.
@shovenose
I was talking about this pay per hour thing he has, also odd that this has happened after node deploy got taken out.
@AnthonySmith Unfortunately the solution to that is not so simple. It's not me. I don't think I have the skills to take a server down for real.
http://xxx
I literally copy and pasted that into the closest VPS at hand - happened to be a CatalystHost VPS.
Then I proceeded to type in host's names.
Didn't intend to do any actual damage, just see whether it works. To clarify, NodeDeploy's SITE NEVER ACTUALLY WENT DOWN!
I tested two other LEB hosts for vulnerability. SITES WERE DOWN FOR LITERALLY 5-10 seconds while I tried to F5 in my browser. Then I cancelled it.
What in hell?
Why is Shovey running such?
What is the "reasoning" behind his action there.
I mean we all know NodeDeploy has been getting banged up and is on hawk watch.. Doh!
Is this why we had a weird network blip earlier today?
shovehost.com is hosted on a pay per hour provider (DigitalOcean)
@jarland
By Pay Per Hour I meant Dgt*l Oc**n
I literally copy and pasted that into the closest VPS at hand - happened to be a CatalystHost VPS.
Then I proceeded to type in host's names.
Didn't intend to do any actual damage, just see whether it works. To clarify, NodeDeploy's SITE NEVER ACTUALLY WENT DOWN!
I tested two other LEB hosts for vulnerability. SITES WERE DOWN FOR LITERALLY 5-10 seconds while I tried to F5 in my browser. Then I cancelled it.
Ban hammer?
@liam
@Damian nope, didn'nt do IPXcore.
1) I proceeded to type in host's names.
2) Didn't intend to do any actual damage, just see whether it works
3) I tested two other LEB hosts for vulnerability
@pubcrawler may I call for my hammer of ban now, it seems appropriate?
This is the point where you need banning, seriously. I'm sure @Jarland wont be happy either.
@Patrick as a result of my findings both not only my own website (ShoveHost.com) is being switched to Apache, but also the two vulnerable hosts are being contacted with some ways to fix the problem so this attack can't get them.
Shovenose, you can't go using hacker tools against other folks. Even if they say alright unless the server you are using is your own and no other folks getting impacted (fine to sh1T can your own server and customers).
Oy Vey!
amazing..
@AnthonySmith, you still have the vat of tar and feathers?
Ban hammers? F**K pitchfork and spit time.
Hands tied on this one. In legal matters I always compress evidence and I will not pay legal fees to protect someone for violating US law under my care.
I do not believe that shovenose knew the implications of his actions. It was shut down quickly on our server. Don't know about the others.
hmm..?
What else is new?
"h4ck Ya L!fe" is definitely a legit name for a blog.