You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on May 19, 2025. It is now read-only.
Addresses #7
- Tolerance levels configurable in Admin area
- Grey listing vs blacklisting levels defined
- Only Greylisted visitors can use click-through link
Copy file name to clipboardExpand all lines: README.md
+24-17Lines changed: 24 additions & 17 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -3,16 +3,17 @@ An implimentation of Project Honeypot's http:BL for YOURLS
3
3
4
4
http:BL is a black list service from [Project Honeypot](https://www.projecthoneypot.org) with an API that is trivial to hook into. While other spam management services & plugins, such as [Phishtank](https://github.com/joshp23/YOURLS-Phishtank-2.0), can check outgoing links, content submissions, and re-check old redirects, Project Honeypot's http:BL acts as a gatekeeper, stopping malicious users at the door before they can do any damage.
5
5
6
-
This plugin can help filter out spam submissions on a YOURLS public interface _and_ on the API. It will redirect any bad IP to an informative and customization friendly block/intercept page written with Bootstrap where any human users will be able to easily set a cookie and access the YOURLS installation. For the API users, it will simply send back an Error 403.
6
+
This plugin can help filter out spam submissions on a YOURLS public interface _and_ on the API. It will redirect any bad IP to an informative and customization friendly block/intercept page written with Bootstrap. If greylisted, any human users will be able to easily set a cookie and access the YOURLS installation. For the API users, it will simply send back an Error 403.
7
7
8
8
Here are a few of HTTP:BL's features
9
9
10
-
1. All logs and settings are in the admin interface, no hand editing of any files (unless you want to)
11
-
2. Use a custom intercept page for flagged IP's. Edit the template, or redirect to your own URL.
12
-
3. Granular log keeping: log only event types that you want, or none at all.
13
-
4. Flush the log table and start fresh whenever you want.
14
-
5. Self-managing: this plugin will (optionally) drop its tables when deactivated, and will create its own tables on activation.
15
-
6. Whitelist IP addressess to skip checks; autodetection of and 1-click addition of the current IP.
10
+
1. All logs and settings are in the admin interface, no hand editing of any files (unless you want to).
11
+
2. Configure threshold levels for blocking and greylisting per threat type (or use defaults for ease of use).
12
+
3. Use either native YOURLS style or a custom intercept page for flagged IP's. Edit the template, or redirect to your own URL.
13
+
4. Granular log keeping: log only event types that you want, or none at all.
14
+
5. Flush the log table and start fresh whenever you want.
15
+
6. Self-managing: this plugin will (optionally) drop its tables when deactivated, and will create its own tables on activation.
16
+
7. Whitelist IP addressess to skip checks; autodetection and 1-click addition of the current IP.
16
17
17
18
## REQUIREMENTS
18
19
@@ -25,19 +26,25 @@ Here are a few of HTTP:BL's features
25
26
1. Place the httpBL folder in YOURLS/user/plugins/
26
27
2. Activate http:BL for Yourls in the Admin interface - sql tables should be made automatically
27
28
3. Set options in the HTTP:BL options page. The default options are just fine. Clicking submit on various forms will enter the default values into the sql tables, but null values all fall back to default actions as well.
28
-
29
-
30
-
#### NOTE: In order for this to work on your public page you have to make sure that
#### comes before anything else. If you are using the [Sleaky](https://github.com/Flynntes/Sleeky) interface, edit your Index.php file to put the above line before
36
-
```
29
+
4. If using a custom URL for blocking, please note the following requests that will be sent to your URL
30
+
- `action` grey or blacklist
31
+
- `ip` the offending IP address
32
+
- `type` the threat type (eg: content spammer)
33
+
- `level` the threat level (0-255)
34
+
35
+
#### NOTE:
36
+
In order for this to work on your public page you have to make sure that
comes before anything else. If you are using the [Sleaky](https://github.com/Flynntes/Sleeky) interface, edit `index.php` to put the above line before
42
+
```
37
43
include 'header.php';
38
44
```
39
45
40
-
#### NOTE: The sql table may need to be added manually using httpBL/assets/httpBL.sql
46
+
#### NOTE:
47
+
The sql table may need to be added manually using `httpBL/assets/httpBL.sql`
41
48
42
49
### TODO:
43
50
1. Add dynamic and randomized honeypot "quicklinks" to all rendered pages - this will likely come in the form of a custom index page, or footer script.
0 commit comments