Skip to content

Conversation

zolotarev
Copy link

No description provided.

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
Copy link

gitguardian bot commented Aug 11, 2025

⚠️ GitGuardian has uncovered 1 secret following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

Since your pull request originates from a forked repository, GitGuardian is not able to associate the secrets uncovered with secret incidents on your GitGuardian dashboard.
Skipping this check run and merging your pull request will create secret incidents on your GitGuardian dashboard.

🔎 Detected hardcoded secret in your pull request
GitGuardian id GitGuardian status Secret Commit Filename
- - Basic Auth String 0564f5f src/common/core/adidos/plugin.json View secret
🛠 Guidelines to remediate hardcoded secrets
  1. Understand the implications of revoking this secret by investigating where it is used in your code.
  2. Replace and store your secret safely. Learn here the best practices.
  3. Revoke and rotate this secret.
  4. 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


🦉 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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant