Browse Source

update SECURITY.md

Rigel Kent 11 months ago
parent
commit
aa8c795674
No account linked to committer's email address
1 changed files with 9 additions and 6 deletions
  1. 9
    6
      SECURITY.md

+ 9
- 6
SECURITY.md View File

@@ -1,8 +1,6 @@
1
-**Introduction**
2
-
3 1
 Security is core to our values, and we value the input of hackers acting in good faith to help us maintain a high standard for the security and privacy for our users. This includes encouraging responsible vulnerability research and disclosure. This policy sets out our definition of good faith in the context of finding and reporting vulnerabilities, as well as what you can expect from us in return.
4 2
 
5
-**Expectations**
3
+## Expectations
6 4
 
7 5
 When working with us according to this policy, you can expect us to:
8 6
 - Extend Safe Harbor (see below) for your vulnerability research that is related to this policy;
@@ -10,7 +8,7 @@ When working with us according to this policy, you can expect us to:
10 8
 - Work to remediate discovered vulnerabilities in a timely manner; and
11 9
 - Recognize your contribution to improving our security if you are the first to report a unique vulnerability, and your report triggers a code or configuration change.
12 10
 
13
-**Safe Harbor**
11
+## Safe Harbor
14 12
 
15 13
 When conducting vulnerability research according to this policy, we consider this research to be:
16 14
 - Authorized in accordance with the law, and we will not initiate or support legal action against you for accidental, good faith violations of this policy;
@@ -22,7 +20,7 @@ You are expected, as always, to comply with all applicable laws.
22 20
 
23 21
 If at any time you have concerns or are uncertain whether your security research is consistent with this policy, please submit a report through one of our Official Channels before going any further.
24 22
 
25
-**Ground Rules**
23
+## Ground Rules
26 24
 
27 25
 To encourage vulnerability research and to avoid any confusion between good-faith hacking and malicious attack, we ask that you:
28 26
 - Play by the rules. This includes following this policy, as well as any other relevant agreements. If there is any inconsistency between this policy and any other relevant terms, the terms of this policy will prevail.
@@ -35,10 +33,15 @@ To encourage vulnerability research and to avoid any confusion between good-fait
35 33
 - You should only interact with test accounts you own or with explicit permission from the account holder.
36 34
 - Do not engage in extortion.
37 35
 
38
-**Official Channels**
36
+## Disclosure Terms
37
+
38
+The vulnerability is kept private until a majority of instances known on instances.joinpeertube.org have updated to a safe version of PeerTube or applied a hotfix. The PeerTube development team coordinates efforts to update once the patch is issued.
39
+
40
+## Official Channels
39 41
 
40 42
 To help us receive vulnerability submissions we use the following official reporting channels:
41 43
 - chocobozzz@cpy.re (GPG: [583A612D890159BE](https://keybase.io/chocobozzz/pgp_keys.asc?fingerprint=c44aad638367912ca93edd57583a612d890159be))
44
+- sendmemail@rigelk.eu (GPG: [EA12971B0E438F36](https://api.github.com/users/rigelk/gpg_keys))
42 45
 
43 46
 If you think you have found a vulnerability, please include the following details with your report and be as descriptive as possible:
44 47
 - The location and nature of the vulnerability,

Loading…
Cancel
Save