Files
Shadowwalker 8a6775bf63 Create SECURITY.md with security policy details
Added a comprehensive security policy outlining vulnerability reporting, cryptographic security, input validation, and best practices.
2025-12-23 06:08:03 +00:00

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:

        1. Description: Clear description of the vulnerability
          1. Location: File paths, line numbers, and functions affected
            1. Impact: Potential impact of the vulnerability
              1. Reproduction: Steps to reproduce the issue (if possible)
                1. Suggested Fix: Any suggestions for fixing the issue (optional)

                2. Security Considerations

                3. Cryptographic Security

                4. CryptoNoise-Ksampler uses SHA-256 for cryptographic operations. The security of the system depends on:

                  • Secret Key Management: Keep your artist_key confidential
                    • 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:

                              1. We will assess the impact
                                1. We will update the dependency or implement a workaround
                                  1. We will release a security patch

                                  2. Supported Versions

                                  3. 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:

                                          1. Keep your ComfyUI installation updated
                                            1. Use strong, unique artist keys
                                              1. Protect your artist keys as you would any cryptographic secret
                                                1. Verify workflow integrity before running workflows from untrusted sources
                                                  1. Keep Python and dependencies up to date

                                                  2. Responsible Disclosure

                                                  3. 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!