Security updates are provided for the latest version of Subtitle Manager. Please use the latest version to ensure you have the most recent security fixes.

Security vulnerabilities should be reported responsibly. Please help keep Subtitle Manager secure by reporting any security issues you find.

Please do not report security vulnerabilities through public GitHub issues.

Instead, please report security vulnerabilities by:

1. GitHub Security Advisories: Use GitHub's private vulnerability reporting feature (preferred)
2. Direct Contact: Reach out through the repository's communication channels

When reporting a vulnerability, please include:

• Description: A clear description of the vulnerability
• Impact: What could an attacker accomplish by exploiting this?
• Reproduction: Steps to reproduce the vulnerability
• Environment: Version numbers, operating system, configuration details
• Suggested Fix: If you have ideas for how to fix the issue (optional)

As a single-maintainer project, I'll do my best to respond to security reports and address issues as time permits. Security fixes will be prioritized, but please understand that response times may vary depending on availability and the complexity of the issue.

• Keep Subtitle Manager updated to the latest version
• Use strong, unique passwords for user accounts
• Enable OAuth2 authentication when available
• Use HTTPS for web interface access
• Monitor logs for suspicious activity

• Follow secure coding practices
• Validate all inputs and sanitize outputs
• Regularly update dependencies and monitor for vulnerabilities
• Test security controls before deployment

• Proposed Security Updates - Security enhancement plans
• Technical Design Security - Architecture security details
• GitHub Security Guidelines - Development security practices

For security-related questions or concerns that are not vulnerabilities, please open a regular GitHub issue.

This security policy is subject to change. Please check back regularly for updates.