Tim Kientzle
dbaf6794c4
I consider this an experiment to see if we can improve the quality of incoming PRs.
27 lines
1.1 KiB
Markdown
27 lines
1.1 KiB
Markdown
# Security Policy
|
|
|
|
If you have discovered a security vulnerability in this project,
|
|
please report it privately.
|
|
**Do not disclose it as a public issue.**
|
|
This gives us time to work with you to fix the issue before public exposure,
|
|
reducing the chance that the exploit will be used before a patch is released.
|
|
|
|
You may submit the report in the following ways:
|
|
|
|
- send an email to security@libarchive.de; and/or
|
|
- send us a [private vulnerability report](https://github.com/libarchive/libarchive/security/advisories/new)
|
|
|
|
Please provide the following information in your report:
|
|
|
|
- A description of the vulnerability and its impact
|
|
- How to reproduce the issue
|
|
|
|
While we welcome all reports, we can act most quickly if the report
|
|
includes a complete libarchive test case and a proposed fix.
|
|
See [doc/WRITING_TESTS.md](doc/WRITING_TESTS.md) for guidance on creating a reproduction test case.
|
|
You can provide the test case and proposed fix as separate patch files
|
|
prepared with `git format-patch` or `git diff`.
|
|
|
|
This project is maintained by volunteers on a reasonable-effort basis.
|
|
We ask that you give us 90 days to work on a fix before public exposure.
|