-
Notifications
You must be signed in to change notification settings - Fork 12
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
[Docs] Beta TestNet - Supplier Cheatsheet #947
Conversation
Update links to RPC endpoints, faucet & explorers
2948a54
to
2db06ee
Compare
d952e5c
to
0c0794b
Compare
|
GitGuardian id | GitGuardian status | Secret | Commit | Filename | |
---|---|---|---|---|---|
13506804 | Triggered | Generic High Entropy Secret | 8d64e2a | localnet/kubernetes/config-path-1.yaml | View secret |
14150880 | Triggered | Generic High Entropy Secret | 8d64e2a | localnet/kubernetes/config-path-3.yaml | View secret |
14150881 | Triggered | Generic High Entropy Secret | 8d64e2a | localnet/kubernetes/config-path-2.yaml | 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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you for putting this together!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Followed the instructions of the guide and had a flawless outcome.
Besides a couple of NITs, it looks good to me 👍
If `grpc-insecure=false`, then it **MUST** be an HTTPS port, with TLS. | ||
|
||
The Grove team exposed one such endpoint on one of our validators for Beta Testnet at `https://shannon-testnet-grove-grpc.beta.poktroll.com:443`. | ||
It can be validated with `grpcurl https://shannon-testnet-grove-grpc.beta.poktroll.com:443`; note no `-plaintext` flag meaning no TLS encryption. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It can be validated with `grpcurl https://shannon-testnet-grove-grpc.beta.poktroll.com:443`; note no `-plaintext` flag meaning no TLS encryption. | |
It can be validated with `grpcurl https://shannon-testnet-grove-grpc.beta.poktroll.com:443`; note the absence of the `-plaintext` flag meaning no TLS encryption. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Co-authored-by: Dima K. <[email protected]>
Co-authored-by: Bryan White <[email protected]> Co-authored-by: Dima K. <[email protected]>
Co-authored-by: Bryan White <[email protected]>
Co-authored-by: Bryan White <[email protected]>
Co-authored-by: Bryan White <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great improvements!
- Warning emojis are catching attention very well
- Noticeable improvement on the
--grpc-insecure
section
Summary
Adding the Supplier cheatsheet!
Issue
Type of change
Select one or more from the following:
consensus-breaking
label if so. See [Infra] Automatically add theconsensus-breaking
label #791 for detailsTesting