mirror of
https://github.com/pterodactyl/panel.git
synced 2024-11-24 01:52:30 +01:00
20 lines
1.1 KiB
Markdown
20 lines
1.1 KiB
Markdown
|
# Security Policy
|
||
|
|
|
||
|
|
## Supported Versions
|
||
|
|
The following versions of Pterodactyl are receiving active support and maintenance. Any security vulnerabilities discovered must be reproducible in supported versions.
|
||
|
|
|
||
|
|
| Panel | Daemon | Supported |
|
||
|
|
| ----- | ------------ | ------------------ |
|
||
|
|
| 1.0.x | wings@1.0.x | :white_check_mark: |
|
||
|
|
| 0.7.x | daemon@0.6.x | :white_check_mark: |
|
||
|
|
| 0.6.x | daemon@0.5.x | :x: |
|
||
|
|
| 0.5.x | daemon@0.4.x | :x: |
|
||
|
|
|
||
|
|
## Reporting a Vulnerability
|
||
|
|
|
||
|
|
Please reach out directly to any project team member on Discord when reporting a security vulnerability, or you can send an email to `dane [ät] pterodactyl.io`.
|
||
|
|
|
||
|
|
We make every effort to respond as soon as possible, although it may take a day or two for us to sync internally and determine the severity of the report and its impact. Please, _do not_ use a public facing channel or GitHub issues to report sensitive security issues.
|
||
|
|
|
||
|
|
As part of our process, we will create a security advisory for the affected versions and disclose it publicly, usually two to four weeks after a releasing a version that addresses it.
|