Conversation
…ssion management, and participant event processing. Update Go module version and dependencies. Add README documentation for the coordinator and its components.
…entity management, and session handling. Introduce badger storage for session artifacts and implement NATS messaging topics for peer communication.
…mes, including YAML configuration files. Introduce a coordinator client for key generation requests and enhance logging throughout the runtime processes. Update .gitignore to include new configuration files.
…ntity handling. Introduce validation and default application for configuration parameters. Implement transport abstraction for NATS messaging, improving session management and peer communication. Add new interfaces for storage management of preparams, shares, and session artifacts.
…ludes source file name. Update Error function to skip an additional stack frame for accurate caller reporting.
…. Introduce Relay interface for unified messaging operations, enhancing configuration management and session handling. Update runtime to utilize relay abstraction, improving flexibility and maintainability.
…duce configuration management for relay settings, including credential loading and topic mapping. Implement runtime for handling MQTT and NATS messaging, enhancing session management and peer communication.
…type. Enhance NATS relay initialization with TLS support and credential management. Update validation logic to ensure required fields are checked for NATS relay provider.
…introduce ECDSA preparams handling. Update .gitignore to include new configuration files and dependencies. Improve session management with default values for configuration parameters.
… initialization and improving key generation request handling. Introduce UUID-based wallet ID generation and update validation logic to ensure proper session management. Refactor configuration management to apply default values and validate required fields, enhancing overall robustness.
…ement request and validation logic for signing operations, including participant management and session handling. Enhance client functionality with detailed error logging and timeout management for improved reliability.
… signing examples to use hex decoding for public keys. Enhance error messages in coordinator validation logic for better clarity. Improve logging in cosigner runtime to include identity public key in startup messages.
…cosigners. Include configuration details, run order, and troubleshooting steps for coordinator, relay, and cosigner nodes.
…and various source files. This change ensures consistency in the usage of the mpcium-sdk across the project.
…ls on directory structure and `go.mod` replace directive for seamless integration of the SDK during local development.
|
Review the following changes in direct dependencies. Learn more about Socket for GitHub.
|
|
| GitGuardian id | GitGuardian status | Secret | Commit | Filename | |
|---|---|---|---|---|---|
| 30450281 | Triggered | Generic High Entropy Secret | ac85dea | cosigner2.config.yaml | View secret |
| 30450279 | Triggered | Generic High Entropy Secret | ac85dea | cosigner.config.yaml | View secret |
| 30450279 | Triggered | Generic High Entropy Secret | d36a786 | cosigner.config.yaml | View secret |
| 30450281 | Triggered | Generic High Entropy Secret | d36a786 | cosigner2.config.yaml | View secret |
| 30450280 | Triggered | Generic High Entropy Secret | d36a786 | coordinator.config.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.
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.