Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Create SECURITY.md #5214

Merged
merged 2 commits into from
Apr 24, 2020
Merged

Create SECURITY.md #5214

Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
e7ef667
Create SECURITY.md
benmcgarry Apr 24, 2020
72ec69f
Update SECURITY.md
benmcgarry Apr 24, 2020
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Update SECURITY.md
  • Loading branch information
@benmcgarry
benmcgarry authored Apr 24, 2020
commit 72ec69f5d37b1f3c4b2c7bd04a30547fb3405da3
4 changes: 2 additions & 2 deletions SECURITY.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -22,6 +22,6 @@ Mozilla Firefox ESR 68: We will backport depending on the impact of the vulnerab

## Reporting a Vulnerability

In order to report a vulnerability, please send an initial email to: ben@redditenhancementsuite.com and we will respond confirming providing a public PGP key for future communications. Please provide as much detail as possible for initial triage.
In order to report a vulnerability, please send an initial email to: ben@redditenhancementsuite.com and we will respond confirming the report. A public PGP key will be provided for future communications. Please provide as much detail as possible for initial triage, if you would rather report under the PGP key please let us know on the email above.

We will aim to respond in 24 hours, if you do not get a response in this timeframe place raise a GitHub Issue stating you are having problems contacting us.
We will aim to respond in 24 hours, if you do not get a response in this timeframe place raise a GitHub issue stating you are having problems contacting us.