27 lines
1.2 KiB
Markdown
27 lines
1.2 KiB
Markdown
|
# Security Policy
|
||
|
|
|
||
|
|
## Supported Versions
|
||
|
|
|
||
|
|
Use this section to tell people about which versions of your project are
|
||
|
|
currently being supported with security updates.
|
||
|
|
|
||
|
|
| Version | Supported |
|
||
|
|
| ------- | ------------------ |
|
||
|
|
| 2.x | :white_check_mark: |
|
||
|
|
| < 2.0 | :x: |
|
||
|
|
|
||
|
|
## Reporting a Vulnerability
|
||
|
|
|
||
|
|
Vulnerabilities should be reported to filebrowser@googlegroups.com - which is a private, maintainer-only group. Maintainers will attempt to respond to/confirm reports within 2-3 days, but if you believe your report to be "critical" to user safety and security, please note as such in the subject. We have tens of thousands of users using our software, and take security vulnerabilities seriously.
|
||
|
|
|
||
|
|
When reporting an issue, where possible, please provide at least:
|
||
|
|
|
||
|
|
* The commit version the issue was identified at
|
||
|
|
* A proof of concept (plaintext; no binaries)
|
||
|
|
* Steps to reproduce
|
||
|
|
* Your recommended remediation(s), if any.
|
||
|
|
|
||
|
|
The FileBrowser team is a volunteer-only effort, and may reach back out for clarification.
|
||
|
|
|
||
|
|
> Note: Please do not open public issues for security issues, as GitHub does not provide facility for private issues, and deleting the issue makes it hard to triage/respond back to the reporter.
|