9bdcbe0447
Major integrations and fixes: - Added BACKBEAT SDK integration for P2P operation timing - Implemented beat-aware status tracking for distributed operations - Added Docker secrets support for secure license management - Resolved KACHING license validation via HTTPS/TLS - Updated docker-compose configuration for clean stack deployment - Disabled rollback policies to prevent deployment failures - Added license credential storage (CHORUS-DEV-MULTI-001) Technical improvements: - BACKBEAT P2P operation tracking with phase management - Enhanced configuration system with file-based secrets - Improved error handling for license validation - Clean separation of KACHING and CHORUS deployment stacks 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com>
21 lines
939 B
Markdown
21 lines
939 B
Markdown
# Security Policy
|
|
|
|
go-libp2p is still in development. This means that there may be problems in our protocols,
|
|
or there may be mistakes in our implementations.
|
|
We take security vulnerabilities very seriously. If you discover a security issue,
|
|
please bring it to our attention right away!
|
|
|
|
## Reporting a Vulnerability
|
|
|
|
If you find a vulnerability that may affect live deployments -- for example, by exposing
|
|
a remote execution exploit -- please [**report privately**](https://github.com/libp2p/go-libp2p/security/advisories/new).
|
|
Please **DO NOT file a public issue**.
|
|
|
|
If the issue is an implementation weakness that cannot be immediately exploited or
|
|
something not yet deployed, just discuss it openly.
|
|
If you need assistance, please reach out to [security@libp2p.io](mailto:security@libp2p.io).
|
|
|
|
## Reporting a non security bug
|
|
|
|
For non-security bugs, please simply file a GitHub [issue](https://github.com/libp2p/go-libp2p/issues/new).
|