-
Notifications
You must be signed in to change notification settings - Fork 111
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
Robe/calamari legacy #1322
base: main
Are you sure you want to change the base?
Robe/calamari legacy #1322
Conversation
|
GitGuardian id | GitGuardian status | Secret | Commit | Filename | |
---|---|---|---|---|---|
13473461 | Triggered | Generic Password | 385ceab | source/Calamari.FullFrameworkTools.Tests/Command/CommandRequestInvokerTests.cs | View secret |
13473461 | Triggered | Generic Password | 0dd875c | source/Calamari.FullFrameworkTools.Tests/Command/CommandRequestInvokerTests.cs | View secret |
13473461 | Triggered | Generic Password | d6c88ca | source/Calamari.FullFrameworkTools.Tests/Command/CommandRequestInvokerTests.cs | 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.
4516f53
to
b2d7e28
Compare
d4ef787
to
63dbb2e
Compare
6d062dc
to
eb1da3d
Compare
No description provided.