hickory-dns/fuzz
Jorge Aparicio ed192864f3 refactor the Resource data structure
the `rr_type` field has been removed. this eliminates the possibility of
setting `rdata` to a type that does not match `rr_type`. as a
consequence, the `set_record_type` has also been removed

the `record_type` of the `Resource` is now derived from what's stored in
the `rdata` field

`rdata` is no longer an `Option`. `rdata = None` was being used to
represent update records. an `Update` variant has been added to the
`RData` enum. this variant is used to represent update records, which
have RDLENGTH set to 0.

the `Resource::{default,new}` constructors have been removed. they felt
error prone as in most cases one wants to set the `rdata` and `name`
fields since they have no sensible defaults. all uses of those
constructors now use the pre-existing `from_rdata` constructor

the `Resource::with` constructor has also been removed. it was pretty
similar to `from_rdata` but initialized `rr_type` and not `rdata`. all
uses of `Record::with` has been changed to `from_rdata`
2024-06-10 20:00:48 -07:00
..
fuzz_targets refactor the Resource data structure 2024-06-10 20:00:48 -07:00
Cargo.toml Prepare 0.24 release with branding change to Hickory DNS (#2054) 2023-10-13 18:39:28 -07:00
README.md add README to the fuzz crate 2022-02-08 00:58:14 +01:00

Fuzzing

There are some basic fuzzing configurations in fuzz_targets. These can be run simply with:

&> cargo fuzz run message --sanitizer=none -- -max_len=1500 -use_value_profile=1

Ideally this should run for an indefinite period of time before finding an issue.