Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Appearance settings

Commit e856fa2

Browse filesBrowse files
TrottMylesBorins
authored andcommitted
doc: simplify security reporting text
Edit security-reporting text in the README to keep it concise and straightforward. The removed text may discourage reporting. Nothing like it appears in similar security-reporting text that I have reviewed. See, for example, the Linux kernel docs on security reporting: https://www.kernel.org/doc/html/v4.11/admin-guide/security-bugs.html PR-URL: #23686 Reviewed-By: Luigi Pinca <luigipinca@gmail.com> Reviewed-By: Ruben Bridgewater <ruben@bridgewater.de>
1 parent 11eabba commit e856fa2
Copy full SHA for e856fa2

File tree

Expand file treeCollapse file tree

1 file changed

+4
-9
lines changed
Open diff view settings
Filter options
Expand file treeCollapse file tree

1 file changed

+4
-9
lines changed
Open diff view settings
Collapse file

‎README.md‎

Copy file name to clipboardExpand all lines: README.md
+4-9Lines changed: 4 additions & 9 deletions
  • Display the source diff
  • Display the rich diff
Original file line numberDiff line numberDiff line change
@@ -166,15 +166,10 @@ team has addressed the vulnerability.
166166
The security team will acknowledge your email within 24 hours. You will receive
167167
a more detailed response within 48 hours.
168168

169-
There are no hard and fast rules to determine if a bug is worth reporting as
170-
a security issue. The general rule is an issue worth reporting should allow an
171-
attacker to compromise the confidentiality, integrity, or availability of the
172-
Node.js application or its system for which the attacker does not already have
173-
the capability.
174-
175-
To illustrate the point, here are some examples of past issues and what the
176-
Security Response Team thinks of them. When in doubt, however, please do send
177-
us a report nonetheless.
169+
There are no hard and fast rules to determine if a bug is worth reporting as a
170+
security issue. Here are some examples of past issues and what the Security
171+
Response Team thinks of them. When in doubt, please do send us a report
172+
nonetheless.
178173

179174

180175
### Public disclosure preferred

0 commit comments

Comments
0 (0)
Morty Proxy This is a proxified and sanitized view of the page, visit original site.