Potential denial-of-service attack methods against the exozyme server #38
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
There are a lot of ways people can attack the server. Here's a few that I thought of:
I mean, we're assuming that the users are people that I kind of know, so we should be able to manage it when something like this happens.
Obvious countermeasures include setting a disk quota and systemd resource limits. I don't think it's needed right now.
OK, it might be time for setting some limits...
Memory leaks like this one will get killed pretty quickly by the OOM killer:
Now time to test fork bombs...
So fork bombs do work, but it's quite easy to stop them by logining in with SSH and running
nice -20 pkill -9 -u USER
. Closing this for now but we can reopen this if we find other attack methods.