Skip to content

Security: imansprn/registry

Security

SECURITY.md

Security Policy

Supported Versions

We actively support the latest version of this project. Security updates will be provided for:

Version Supported
Latest
< Latest

Reporting a Vulnerability

If you discover a security vulnerability, please do not open a public issue. Instead, please report it privately using one of the following methods:

Option 1: GitHub Security Advisories (Recommended)

  1. Go to the Security tab in the repository
  2. Click on Report a vulnerability
  3. Fill out the security advisory form

Option 2: Email

Send an email to [INSERT YOUR EMAIL OR SECURITY EMAIL] with:

  • A clear description of the vulnerability
  • Steps to reproduce the issue
  • Potential impact
  • Suggested fix (if any)

What to Expect

  • Acknowledgment: You will receive an acknowledgment within 48 hours
  • Initial Assessment: We will provide an initial assessment within 7 days
  • Updates: We will keep you informed of our progress
  • Resolution: We will work to resolve the issue as quickly as possible

Disclosure Policy

  • We will coordinate with you on the disclosure timeline
  • Vulnerabilities will be disclosed after a fix is available
  • You will be credited for the discovery (unless you prefer to remain anonymous)

Security Best Practices

When using this Docker registry:

  1. Use Strong Passwords: Generate passwords with at least 16 characters
  2. Enable TLS: Always use TLS in production environments
  3. Keep Updated: Regularly update the registry image for security patches
  4. Network Security: Restrict access using firewall rules and VPNs
  5. Regular Audits: Regularly review and rotate credentials and secrets

Known Security Considerations

  • This registry uses basic authentication (htpasswd). For production, consider additional security layers.
  • TLS is recommended but not enforced by default - configure it for production use.
  • The registry runs with default Docker Registry security settings - review and harden as needed for your use case.

There aren’t any published security advisories