diff options
| author | Rich Trott <rtrott@gmail.com> | 2018-10-19 21:07:50 +0300 |
|---|---|---|
| committer | Myles Borins <mylesborins@google.com> | 2018-11-29 19:39:05 +0300 |
| commit | 0b1e41799d9d1c758045af12979c0e7be47c2d78 (patch) | |
| tree | dacfb4bc14e55b89f9e30a25046cfd649fd72f96 /README.md | |
| parent | 5844932b6c65bfc442458793be2173d31462df39 (diff) | |
doc: revise security-reporting example text
Edit for simplicity and clarity.
PR-URL: https://github.com/nodejs/node/pull/23759
Reviewed-By: Sam Roberts <vieuxtech@gmail.com>
Reviewed-By: Matheus Marchini <mat@mmarchini.me>
Reviewed-By: Vladimir de Turckheim <vlad2t@hotmail.com>
Reviewed-By: Ben Noordhuis <info@bnoordhuis.nl>
Diffstat (limited to 'README.md')
| -rw-r--r-- | README.md | 16 |
1 files changed, 7 insertions, 9 deletions
diff --git a/README.md b/README.md index 5c5848313ac..540c0ed18c8 100644 --- a/README.md +++ b/README.md @@ -175,17 +175,15 @@ nonetheless. ### Public disclosure preferred - [#14519](https://github.com/nodejs/node/issues/14519): _Internal domain - function can be used to cause segfaults_. Causing program termination using - either the public JavaScript APIs or the private bindings layer APIs requires - the ability to execute arbitrary JavaScript code, which is already the highest - level of privilege possible. + function can be used to cause segfaults_. Requires the ability to execute + arbitrary JavaScript code. That is already the highest level of privilege + possible. - [#12141](https://github.com/nodejs/node/pull/12141): _buffer: zero fill - Buffer(num) by default_. The buffer constructor behavior was documented, - but found to be prone to [mis-use](https://snyk.io/blog/exploiting-buffer/). - It has since been changed, but despite much debate, was not considered misuse - prone enough to justify fixing in older release lines and breaking our - API stability contract. + Buffer(num) by default_. The documented `Buffer()` behavior was prone to + [misuse](https://snyk.io/blog/exploiting-buffer/). It has since changed. It + was not deemed serious enough to fix in older releases and breaking API + stability. ### Private disclosure preferred |