-
Notifications
You must be signed in to change notification settings - Fork 511
Add automated captcha enable plugin #2597
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
Conversation
Add new ADIDOS plugin with monitoring job that enables/disables antibot based on server CPU load. Includes configuration options for thresholds, cooldown period and captcha type. The system periodically checks remote server load via SSH and toggles antibot state accordingly.
Add ssh and curl packages to support additional functionality in the scheduler container
Add ADIDOS_LOG configuration option to enable logging for antibot control. Implement webhook notifications when antibot is enabled/disabled, including load percentage and duration information. Update logic for caching and state management of antibot control.
Initialize config and services variables before database update to prevent potential undefined variable errors
The command was previously extracting the wrong field from top output, showing CPU idle time instead of usage. Updated to properly calculate CPU usage by subtracting idle from 100.
- Add ADIDOS_USE_WEBHOOK setting to enable/disable webhook notifications - Update plugin version from 1.1 to 1.2 - Improve webhook function with enable check and better error handling - Clarify logging help text for load-based antibot control
Feature: Add adidos plugin
|
GitGuardian id | GitGuardian status | Secret | Commit | Filename | |
---|---|---|---|---|---|
- | - | Basic Auth String | 0564f5f | src/common/core/adidos/plugin.json | View secret |
🛠 Guidelines to remediate hardcoded secrets
- Understand the implications of revoking this secret by investigating where it is used in your code.
- Replace and store your secret safely. Learn here the best practices.
- Revoke and rotate this secret.
- If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.
To avoid such incidents in the future consider
- following these best practices for managing and storing secrets including API keys and other credentials
- install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.
🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.
Add comprehensive README for ADIDOS feature including: - System overview and functionality - Configuration settings and options - Docker setup requirements - Example configurations - Troubleshooting and monitoring - Security considerations
docs: add ADIDOS documentation for adaptive DDoS protection system
No description provided.