|Number of watchers on Github||158|
|Number of open issues||3|
|Average time to merge a PR||12 days|
|Open pull requests||4+|
|Closed pull requests||0+|
|Last commit||over 3 years ago|
|Repo Created||about 6 years ago|
|Repo Last Updated||almost 2 years ago|
|Organization / Author||valyala|
|Do you use goloris? Leave a review!|
|View open issues (3)|
|View goloris activity|
|View on github|
|Fresh, new opensource launches 🚀🚀🚀|
Trendy new open source projects in your inbox! View examples
How it works?
It tries occupying and keeping busy as much tcp connections to the victim as possible by using as low network bandwidth as possible. If goloris is lucky enough, then eventually it should eat all the available connections to the victim, so no other client could connect to it. See the source code for more insights.
In a few minutes with default config options.
All up to 1.5.9 if unprotected as described below (i.e. with default config).
I know the following options:
Patch nginx, so it drops connection if the client sends POST body at very slow rate.
go get -u -a github.com/valyala/goloris go build github.com/valyala/goloris ./goloris -help
P.S. Don't forget adjusting
ulimit -n before experimenting.
And remember - goloris is published for educational purposes only.