paritybit.ca

Unnamed repository; edit this file 'description' to name the repository.
Log | Files | Refs | README | LICENSE

commit ff927f8810492b0feeda2e04da17305cfc1be6a1
parent efc08d1c3f738ff2d40a41fb9df369383fac431e
Author: Jake Bauer <jbauer@paritybit.ca>
Date:   Wed, 29 Jul 2020 23:32:54 -0400

More words to latest BP

Diffstat:
Mpages/blog/my-git-server-was-ddosed.md | 2+-
1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/pages/blog/my-git-server-was-ddosed.md b/pages/blog/my-git-server-was-ddosed.md @@ -34,7 +34,7 @@ My next step in diagnosing the problem was to check the server logs. Normally, I have both the `access.log` and `error.log` turned off on my servers because I don't need the content of those logs under normal circumstances. I proceeded to turn on logging again just for [git.paritybit.ca](https://git.paritybit.ca) and -watched them with `tail -f`. +watched them with `tail -f` to try to get an idea of what was going on. I noticed a flood of various sketchy looking user agents constantly hitting various URLs in a pattern that was clearly indicative of bots. These bots were