-
Notifications
You must be signed in to change notification settings - Fork 310
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
v5.32.0 #1419
v5.32.0 #1419
Conversation
Cabecinha84
commented
Oct 29, 2024
- Adds options to allow to adjust number of instances and subscription period on marketplace apps;
- Fix marking node as DOS if another machine is online confirmed on the network with a different ip;
- Uninstall apps if node gets DOS;
- Other small improvements.
… is confirmed and it's running on a different server
* Latest changes * Tidy up * Add tests, remove not need lock removals
|
GitGuardian id | GitGuardian status | Secret | Commit | Filename | |
---|---|---|---|---|---|
8398280 | Triggered | PGP Private Key | 7516f95 | HomeUI/dist/js/index.js | View secret |
8398280 | Triggered | PGP Private Key | 7516f95 | HomeUI/dist/js/index.js | View secret |
8398280 | Triggered | PGP Private Key | dcc4740 | HomeUI/dist/js/index.js | View secret |
8398280 | Triggered | PGP Private Key | dcc4740 | HomeUI/dist/js/index.js | 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 secrets safely. Learn here the best practices.
- Revoke and rotate these secrets.
- 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.