Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Appearance settings

Security: ebogdum/callfs

Security

SECURITY.md

Security Policy

Reporting Security Vulnerabilities

We take the security of CallFS seriously. If you discover a security vulnerability, please report it to us as described below.

Please do not report security vulnerabilities through public GitHub issues.

Instead, please send an email to admin.nxpoint@gmail.com with the following information:

  • Description of the vulnerability
  • Steps to reproduce or proof-of-concept
  • Affected versions
  • Potential impact

We will acknowledge your email within 48 hours and will send a more detailed response within 72 hours indicating the next steps in handling your report.

Supported Versions

Version Supported
0.1.x

Security Measures

CallFS implements several security measures:

  • API key authentication for all endpoints
  • Owner-based access control for files and directories
  • Rate limiting to prevent abuse
  • Input validation and sanitization
  • Secure file path handling to prevent directory traversal
  • TLS encryption for network communication

Security Best Practices

When deploying CallFS:

  1. Use strong, randomly generated API keys
  2. Enable TLS/HTTPS in production
  3. Regularly update to the latest version
  4. Monitor access logs for suspicious activity
  5. Restrict network access to necessary endpoints only
  6. Use appropriate file system permissions

There aren't any published security advisories

Morty Proxy This is a proxified and sanitized view of the page, visit original site.