Skip to content

Security: michaelamoetoevsky/PDN

Security

SECURITY.md

Security Policy

Supported Versions

We provide security updates for the following versions:

Version Supported
0.1.x ✅
< 0.1 ❌

Reporting a Vulnerability

We take security vulnerabilities seriously. If you discover a security vulnerability in PDN, please report it responsibly.

How to Report

Please do NOT create a public GitHub issue for security vulnerabilities.

Instead, please report security vulnerabilities by emailing: security@pdn.example.com

Include the following information:

  • Description of the vulnerability
  • Steps to reproduce
  • Potential impact
  • Affected versions
  • Any suggested fixes (if known)

What to Expect

  1. Acknowledgment: We will acknowledge receipt within 48 hours
  2. Assessment: We will assess the vulnerability and determine severity
  3. Timeline: We will provide an estimated timeline for a fix
  4. Coordination: We will coordinate with you on disclosure timeline
  5. Credit: We will credit you in the security advisory (if desired)

Security Best Practices for Users

Container Security

  • Always use the latest PDN version
  • Keep container images updated
  • Use minimal base images
  • Run containers with least privileges
  • Use resource quotas to limit container resources

Network Security

  • Use PDN's built-in network isolation
  • Avoid exposing unnecessary ports
  • Use TLS for inter-service communication
  • Configure firewall rules on host

Container Images

  • Verify image signatures when possible
  • Use trusted registries
  • Scan images for vulnerabilities
  • Rebuild images regularly

Service Supervisor

  • Use resource quotas to prevent resource exhaustion
  • Configure health checks for all services
  • Set appropriate restart policies
  • Monitor service logs regularly

Known Security Considerations

PRoot Limitations

PDN uses PRoot for containerization, which has known limitations:

  • PRoot uses ptrace for syscall interception
  • Not a full kernel-level isolation (like KVM or gVisor)
  • Some syscalls may not be fully intercepted
  • Not suitable for untrusted code execution

Termux Environment

  • Runs on Android without root
  • Limited by Android's security model
  • SELinux policies may restrict some operations
  • File system permissions differ from standard Linux

Vulnerability Disclosure Timeline

Phase Timeline
Initial Response 48 hours
Triage 7 days
Fix Development 30-90 days (depending on severity)
Release Within 7 days of fix
Public Disclosure After fix released + 7 days

Security Advisories

Security advisories will be published as:

  • GitHub Security Advisories
  • Release notes with security fixes
  • Email notifications to subscribers

Contact

For security-related questions or concerns:


This policy is based on industry best practices and may be updated periodically.

There aren't any published security advisories