rvba/docs
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Actualiser Zurich hackathon

Milovann Yanatchkov 2025-01-01 18:35:05 +01:00
parent 0c34d1c22b
commit f145560e55
1 changed files with 0 additions and 10 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

10
Zurich-hackathon.md

@ -70,13 +70,3 @@ This is made possible thanks to [IfcMerge](https://github.com/brunopostle/ifcmer
* 📨 contact@gitaec.com
## DDoS Mitigation
🚨 **June 28th** : [gitaec.org](https://gitaec.org) is currently offline due to a [DDoS](https://en.wikipedia.org/wiki/Denial-of-service_attack) attack on its git services. We will be back online as soon as possible. In the meantime, you can browse examples on **[gitaec.com](https://gitaec.com/rvba/hackathon-zurich)**.
July, 1st : **The incident is now closed**
✏️ **[Postmortem report](https://en.wikipedia.org/wiki/Postmortem_documentation)** : Starting at the end of June 2024, we began noticing that our forges were slow to respond. We then checked our servers and discover that they were at full CPU capacity, permanently. This was caused by some computationally intensive requests involving git commands such as ``git blame``. We had to shut down our services for a couple of days to find a solution. Our web server logs showed up to 350,000 requests a day targeting git repositories from hundreds of different IPs. But despite this apparent diversity, a single user agent was involved : ``facebookexternalhit``. After some quick research, we found out that we were victims of a DDoS attack [involving a malicious use of the Facebook API](https://developers.facebook.com/community/threads/992798532416685/). By adding a simple user agent test in front of our server proxy (Nginx), we were able to reject these malicious requests. This seems to have "solved" the issue for now.