Skip to content

Commit fa6c194

Browse files
author
MarcoFalke
committed
doc: Adjust links in OSS-Fuzz section
1 parent 90a5786 commit fa6c194

File tree

1 file changed

+5
-7
lines changed

1 file changed

+5
-7
lines changed

doc/fuzzing.md

Lines changed: 5 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -285,13 +285,11 @@ $ ./honggfuzz/honggfuzz --exit_upon_crash --quiet --timeout 4 -n 1 -Q \
285285
# OSS-Fuzz
286286
287287
Bitcoin Core participates in Google's [OSS-Fuzz](https://github.com/google/oss-fuzz/tree/master/projects/bitcoin-core)
288-
program, which includes a dashboard of [publicly disclosed vulnerabilities](https://bugs.chromium.org/p/oss-fuzz/issues/list?q=bitcoin-core).
289-
Generally, we try to disclose vulnerabilities as soon as possible after they
290-
are fixed to give users the knowledge they need to be protected. However,
291-
because Bitcoin is a live P2P network, and not just standalone local software,
292-
we might not fully disclose every issue within Google's standard
288+
program, which includes a dashboard of [publicly disclosed vulnerabilities](https://issues.oss-fuzz.com/issues?q=bitcoin-core%20status:open).
289+
290+
Bitcoin Core follows its [security disclosure policy](https://bitcoincore.org/en/security-advisories/),
291+
which may differ from Google's standard
293292
[90-day disclosure window](https://google.github.io/oss-fuzz/getting-started/bug-disclosure-guidelines/)
294-
if a partial or delayed disclosure is important to protect users or the
295-
function of the network.
293+
.
296294
297295
OSS-Fuzz also produces [a fuzzing coverage report](https://oss-fuzz.com/coverage-report/job/libfuzzer_asan_bitcoin-core/latest).

0 commit comments

Comments
 (0)