Skip to content

Building 70 Projects ranging from beginner to advanced so anyone can β€” learn from, build upon, use as a reference, or even copy directly. Owned by my cybersecurity company πŸ‘‡

docs(lisdex): drop the stream-scope bullet from the README

CarterPerez-devde486b0ec430
diff --git a/PROJECTS/advanced/zero-day-vulnerability-scanner/README.md b/PROJECTS/advanced/zero-day-vulnerability-scanner/README.md
index 1ab4c9ae..d79b0de0 100644
--- a/PROJECTS/advanced/zero-day-vulnerability-scanner/README.md
+++ b/PROJECTS/advanced/zero-day-vulnerability-scanner/README.md
@@ -85,15 +85,6 @@ These are deliberate, and they are the reason to trust the rest of the output.
parameter blocked it.
- **It will not report a planted bug.** Crashes from a benchmark-instrumented
build are stamped NOT DISCLOSABLE with no filing route.
-- **It will not invent a stream for a library that never takes bytes as an
- argument.** lisdex drives entry points that receive the input as a
- *parameter*. Some libraries only accept input the caller has already
- assembled into a stream: openjpeg wants read, seek and skip callbacks over
- its own user-data struct, and libtiff's own fuzz target opens a C++
- `std::istream` through `TIFFStreamOpen`. Neither shape is a parameter, so
- the ranker grades those entry points `NoDataInput` and says so, rather than
- guessing a call sequence no header states. Measured on the six validation
- libraries: four synthesize, those two do not.
## The optional booster