CrowdSec
| 开发者 | crowdsec |
|---|---|
| 更新时间 | 2025年6月13日 13:10 |
| 捐献地址: | 去捐款 |
| PHP版本: | 7.2 及以上 |
| WordPress版本: | 6.8 |
| 版权: | MIT |
| 版权网址: | 版权信息 |
标签
下载
2.11.1
2.0.3
0.5.2
1.0.4
2.9.0
1.1.0
1.1.1
1.2.2
1.2.3
1.2.4
1.2.5
1.3.2
1.4.3
1.5.0
1.4.0
1.5.1
1.8.1
1.4.2
2.6.7
1.4.1
1.7.0
1.9.0
0.5.4
1.0.0
1.0.2
1.0.6
1.11.0
2.0.0
0.5.3
1.0.1
1.0.3
1.0.5
2.0.4
2.1.0
1.0.7
1.3.0
2.3.1
2.4.1
2.5.0
2.5.1
2.5.2
2.3.0
2.4.0
2.6.2
0.6.0
1.1.2
1.3.1
2.10.0
2.11.0
1.10.0
1.6.0
1.8.0
2.0.1
2.2.0
2.6.3
2.6.4
2.6.5
2.6.6
2.7.0
2.0.2
2.6.0
2.6.1
2.8.0
2.8.1
详情介绍:
The CrowdSec plugin proactively blocks requests coming from known attackers.
It does so by either directly using CrowdSec Blocklists Integration or by connecting to your CrowdSec Security Engine.
Key Features:
- Instant CrowdSec Blocklist: Quickly block known WordPress attackers in a few clicks.
- Detect and block admin bruteforce attempts and scans of your WordPress Site.
- Remediation metrics: Enabling you to see the efficiency of the protection.
- (Console Users) Plug any of your existing Blocklist Integrations.
- (CrowdSec Security Engine Users) Apply decisions and subscribed blocklist of your security engine within WordPress. You can:
- Block aggressive IPs
- Display a captcha for less aggressive IPs
安装:
Check Full Documentation for more details
Multiple ways you can use the plugin
- Instant WordPress Blocklist - easiest
- Blocklist as a Service Integration - your blocklist catalog
- Connect it to your CrowdSec Security Engine - advanced & most complete
屏幕截图:
常见问题:
Do I need to install CrowdSec Security Engine?
- Not necessarily, you can connect it directly to a CrowdSec Blocklist Integration endpoint
- Via Instant WordPress Blocklist
- Or Blocklist as a Service Integration
- You can of course connect it to a security engine if you have one
更新日志:
2.11 (2025-06-02)
- Add Blocklist as a Service (BLaaS) subscription button
- Add Usage Metrics table in UI
- Handle BLaaS LAPI specific behavior
- Add usage metrics support
- Disable "Public Website only" setting by default
- Add AppSec component support
- Move logs and cache folders to
wp-content/uploads/crowdsecfolder - Add a
Enable auto_prepend_file modesetting.
- Add WordPress multisite compatibility
- Use absolute path for TLS files
- Use absolute path for geolocation files
- Add an action after plugin upgrade to recreate standalone settings file
- Add access restriction for some folders
- Do not use cache tags
- Do not rotate log files
- Add custom User-Agent debug setting
- All source code has been refactored using new CrowdSec PHP librairies
- Add LAPI request timeout setting
- Modify ban and captcha walls templating for W3C validity
- Add TLS authentication option
- Add
use_curlconfiguration: should be used ifallow_url_fopenis disabled andcurlis available - Add
disable_prod_logconfiguration - Change log path to
wp-content/plugins/crowdsec/logs - By default, the
bouncing_levelsetting is nowbouncing_disabled(instead ofnormal_bouncing)
- Add geolocation feature
- Add "Test bouncing" action in settings view
- Use cache instead of session to store some values
- Do not bounce PHP CLI
- Use static settings only in standalone mode
- Fix issue that cause warning message error on front in standalone mode
- Fix behavior : bounce should not be done twice in standalone mode
- Remove useless configuration to enable standalone mode
- Use
0.14.0version of crowdsec php lib - Handle typo fixing for retro compatibility (
flex_boucing=>flex_bouncingandnormal_boucing=>normal_bouncing) - Split of debug in 2 configurations : debug and display_errors
- Add Standalone mode: an option allowing the PHP engine to no longer have to load the WordPress core during the bouncing stage. To be able to apply this mode, the webmaster has to set the auto_prepend_file PHP flag to the script we provide.
- Add debug mode: user can enable the debug mode directly from the CrowdSec advanced settings panel. A more verbose log will be written when this flag is enabled.
- Add WordPress 5.7 support
- Add PHP 8.0 support