This repository was archived by the owner on Aug 8, 2022. It is now read-only.
418 Teapot poor mans IPS#3
Merged
nomandera merged 3 commits intolinuxserver-labs:devfrom May 15, 2020
nomandera:dev
Merged
Conversation
It is very unlikely you will ever see this status code unless you manually implement it.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This puts in place the basic framework for implementing very basic Intrusion Protection.
The premise is simple, any time you can identify abuse and want it to be counted towards an IP ban send the user a 418, legitimate but weird, status code.
For example if you dont run wordpress or phpmyadmin then any call to either of these very common attack end points can be detected and count towards a block.
This wont achieve an awful lot but the cost is small and every little bit helps.