Skip to content
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

(WIP) spin up audiusd container without audius-docker-compose #10441

Draft
wants to merge 3 commits into
base: main
Choose a base branch
from

Stable base docker image for encoding

43cb00d
Select commit
Loading
Failed to load commit list.
Draft

(WIP) spin up audiusd container without audius-docker-compose #10441

Stable base docker image for encoding
43cb00d
Select commit
Loading
Failed to load commit list.
GitGuardian / GitGuardian Security Checks completed Dec 6, 2024 in 2s

2 secrets uncovered!

2 secrets were uncovered from the scan of 3 commits in your pull request. ❌

Please have a look to GitGuardian findings and remediate in order to secure your code.

Details

🔎 Detected hardcoded secrets in your pull request

  • Pull request #10441: phelpsdb-wrapperless-audiusctl 👉 main
GitGuardian id GitGuardian status Secret Commit Filename
14086629 Triggered Generic Password 4b7f416 cmd/audiusd/entrypoint.sh View secret
11648680 Triggered Generic High Entropy Secret 4b7f416 dev-tools/templates/devnet.yaml 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 secrets safely. Learn here the best practices.
  3. Revoke and rotate these secrets.
  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.