GeezerVison

The World Wide Web, restored to 800 pixels of glory.

GeezerVison is showing github.com — doc: improve security section of README.md · nodejs/node@12db4d9

File tree

Expand file treeCollapse file tree

Open diff view settings

Filter options

README.md

Expand file treeCollapse file tree

Open diff view settings

Collapse file

`‎README.md‎`

Copy file name to clipboardExpand all lines: README.md

+8-9Lines changed: 8 additions & 9 deletions

Display the source diff
Display the rich diff

Original file line number	Diff line number	Diff line change
`@@ -172,20 +172,19 @@ Node.js from source along with a list of officially supported platforms.`
`172`	`172`
`173`	`173`	`## Security`
`174`	`174`
`175`		`-All security bugs in Node.js are taken seriously and should be reported by`
`176`		`-emailing [email protected]. This will be delivered to a subset of the project`
`177`		`-team who handle security issues. Please don't disclose security bugs`
`178`		`-publicly until they have been handled by the security team.`
	`175`	`+Security flaws in Node.js should be reported by emailing [email protected].`
	`176`	`+Please do not disclose security bugs publicly until they have been handled by`
	`177`	`+the security team.`
`179`	`178`
`180`		`-Your email will be acknowledged within 24 hours, and you’ll receive a more`
	`179`	`+Your email will be acknowledged within 24 hours, and you will receive a more`
`181`	`180`	`detailed response to your email within 48 hours indicating the next steps in`
`182`	`181`	`handling your report.`
`183`	`182`
`184`	`183`	`There are no hard and fast rules to determine if a bug is worth reporting as`
`185`		`-a security issue. The general rule is any issue worth reporting`
`186`		`-must allow an attacker to compromise the confidentiality, integrity`
`187`		`-or availability of the Node.js application or its system for which the attacker`
`188`		`-does not already have the capability.`
	`184`	`+a security issue. The general rule is an issue worth reporting should allow an`
	`185`	`+attacker to compromise the confidentiality, integrity, or availability of the`
	`186`	`+Node.js application or its system for which the attacker does not already have`
	`187`	`+the capability.`
`189`	`188`
`190`	`189`	`To illustrate the point, here are some examples of past issues and what the`
`191`	`190`	`Security Response Team thinks of them. When in doubt, however, please do send`

0 commit comments

Comments

0 (0)

You are visitor 01402503 — GeezerVison does not store the pages you look up.
Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required.