Added a comprehensive security policy outlining vulnerability reporting, cryptographic security, input validation, and best practices.
5.3 KiB
Security Policy
Reporting a Vulnerability
We take security seriously. If you discover a security vulnerability in CryptoNoise-Ksampler, please report it responsibly.
Do Not
- Do not open public GitHub issues for security vulnerabilities
-
- Do not share vulnerability details publicly until a fix is available
-
-
Do not disclose the vulnerability to other parties without permission
-
How to Report
-
Please report security vulnerabilities by email to the project maintainers. Include:
-
- Description: Clear description of the vulnerability
-
- Location: File paths, line numbers, and functions affected
-
- Impact: Potential impact of the vulnerability
-
- Reproduction: Steps to reproduce the issue (if possible)
-
-
Suggested Fix: Any suggestions for fixing the issue (optional)
-
Security Considerations
-
Cryptographic Security
-
CryptoNoise-Ksampler uses SHA-256 for cryptographic operations. The security of the system depends on:
-
- Secret Key Management: Keep your
artist_keyconfidential -
- Collision Resistance: SHA-256 is cryptographically secure (collision probability ~10^-77)
-
-
Key Storage: Store artist keys securely, never commit them to version control
-
Input Validation
-
All user inputs should be validated:
-
- Artist keys should be strings of sufficient length
-
- Generation parameters should match expected ranges
-
-
Seed values should be valid integers
-
Dependencies
-
We actively monitor dependencies for known vulnerabilities. If a vulnerability is discovered in a dependency:
-
- We will assess the impact
-
- We will update the dependency or implement a workaround
-
-
We will release a security patch
-
Supported Versions
-
We provide security updates for:
-
- Current Version: Latest release receives security patches
-
- Previous Version: Last major version receives critical patches
-
-
End of Life: Versions older than 1 year may not receive patches
-
Security Best Practices
-
When using CryptoNoise-Ksampler:
-
- Keep your ComfyUI installation updated
-
- Use strong, unique artist keys
-
- Protect your artist keys as you would any cryptographic secret
-
- Verify workflow integrity before running workflows from untrusted sources
-
-
Keep Python and dependencies up to date
-
Responsible Disclosure
-
We follow responsible disclosure practices:
-
- Security reports are addressed within 30 days
-
- Fixes are developed and tested before disclosure
-
-
Credit is given to researchers who report vulnerabilities responsibly
-
-
Coordinated disclosure timeline will be agreed upon
-
Security Updates
-
Security patches will be released as soon as practical after a vulnerability is confirmed and fixed. Critical security vulnerabilities may be backported to previous versions.
Thank you for helping keep CryptoNoise-Ksampler secure!
-
-
-
-
-
-
-
- Secret Key Management: Keep your
-
-