misc_pterodactyl-panel/SECURITY.md

# 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.7.x | wings@1.5.x  | :white_check_mark: |
| 0.7.x | daemon@0.6.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@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.
Create SECURITY.md 2020-05-25 22:08:47 +00:00			`# 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 \|`
			`\| ----- \| ------------ \| ------------------ \|`
Update SECURITY.md 2022-01-20 02:10:51 +00:00			`\| 1.7.x \| wings@1.5.x \| :white_check_mark: \|`
Update SECURITY.md 2021-02-25 04:44:08 +00:00			`\| 0.7.x \| daemon@0.6.x \| :x: \|`
Update SECURITY.md 2021-10-02 15:21:04 +00:00
Create SECURITY.md 2020-05-25 22:08:47 +00:00
			`## Reporting a Vulnerability`

(security) use POST for logout rather than GET see https://github.com/pterodactyl/panel/security/advisories/GHSA-m49f-hcxp-6hm6 2021-10-23 20:00:21 +00:00			Please reach out directly to any project team member on Discord when reporting a security vulnerability, or you can send an email to `dane@pterodactyl.io`.
Create SECURITY.md 2020-05-25 22:08:47 +00:00
			`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.`