My first DDoS attack for a $200 ransom
ghirardotti.fr
My first DDoS attack for a $200 ransom
1–10 of 67 posts
Re: My first DDoS attack for a $200 ransom
#2Apparently, it didn't work. :)
Site not installed The site ghirardotti.fr is not yet installed
[Edit: it's up now.]
Re: My first DDoS attack for a $200 ransom
#3Apparently, it didn't work. :) Site not installed The site ghirardotti.fr is not yet installed [Edit: it's up now.]
Though, it is interesting how an article with a dead link made it on the frontpage with 3 points.
Re: My first DDoS attack for a $200 ransom
#4Apparently, it didn't work. :) Site not installed The site ghirardotti.fr is not yet installed [Edit: it's up now.]
Though, it is interesting how an article with a dead link made it on the frontpage with 3 points.
It's working well for me. And as it's a GitHub website, it should be ok...
Re: My first DDoS attack for a $200 ransom
#5Apparently, it didn't work. :) Site not installed The site ghirardotti.fr is not yet installed [Edit: it's up now.]
Though, it is interesting how an article with a dead link made it on the frontpage with 3 points.
And there are 73 persons on it right now if I believe Google Analytics
Re: My first DDoS attack for a $200 ransom
#6For next time you don't want to have to copy and paste. No need for SED.
cat | cut -d ' ' -f1 | sort | uniq -c | sort -nr
Re: My first DDoS attack for a $200 ransom
#7Earlier quoted context omitted.
Though, it is interesting how an article with a dead link made it on the frontpage with 3 points.
And there are 73 persons on it right now if I believe Google Analytics
[ Edit: I'm almost certain it's an ipv6 vs ipv4 issue. the ipv4 addresses resolve to github pages land, the ipv6 address resolves to somewhere inside OVH - the issue being that if the viewer's network infrastructure prefers ipv6, they will get a holding page from OVH stating that that "Site not installed / The site ghirardotti.fr is not yet installed" ]
Dig:
dig ghirardotti.fr
;; ->>HEADERreverse dns
dig -x 192.30.252.154
; > DiG 9.8.3-P1 > -x 192.30.252.154
;; global options: +cmd
;; Got answer:
;; ->>HEADER dig AAAA ghirardotti.fr
; > DiG 9.8.3-P1 > AAAA ghirardotti.fr
;; global options: +cmd
;; Got answer:
;; ->>HEADER dig -x 2001:41d0:1:1b00:213:186:33:19
; > DiG 9.8.3-P1 > -x 2001:41d0:1:1b00:213:186:33:19
;; global options: +cmd
;; Got answer:
;; ->>HEADERRe: My first DDoS attack for a $200 ransom
#8Roughly, a somewhat lackluster response to a somewhat lackluster DDoS attempt.
They tried blocking specific ip addresses, which didn't work, because the attack was somewhat distributed. They then just turned on some caching, which allowed the site to function, albeit with an unknown excess bandwidth charge pending.
And, the DDoS itself can't of been terribly impressive, as all it took to mitigate was a bit of caching. He mentions 10 requests / sec as the scale of the attack.
Re: My first DDoS attack for a $200 ransom
#9Ummmm.... A cache layer for any web application is a must have, perhaps he could have avoided the attack all along if it were present on the system since day one?...
At least for this kind of attack, a more serious DDoS won't be tamed by "just adding cache"
Re: My first DDoS attack for a $200 ransom
#10For next time you don't want to have to copy and paste. No need for SED. cat | cut -d ' ' -f1 | sort | uniq -c | sort -nr
no need for cat