You cannot select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

Victor Julien e08474a283 nfs: check a v3 WRITE and READ claim against the record ... The args of a WRITE request and of a READ reply were trusted to fit the record that carries them. Where the claim fell below the extent the parse covers, the file data ran past the record boundary into the next RPC, which was then read as a record. A max-tx of 0 was accepted and evicted every transaction on insert. Compare the claim against that extent: for a WRITE the handle, offset, count, stable flag and its data, for a READ the status, the optional attributes, the count, the eof flag and its data. A record whose claim is below the extent gets a transaction with the malformed data event and a skip to the record boundary, as an oversized claim already does. Only the v3 records arrive in pieces, so process_read_record now learns which reply it is given and the check is v3's. Reject a max-tx of 0 at config load. Ticket: #9263.		21 hours ago
..
.cargo	…
derive	rust: inherit common package metadata from workspace	6 days ago
ffi	rust: keep the ffi logger out of the test binary	21 hours ago
htp	rust: hoist nom 8 dependency into workspace	6 days ago
src	nfs: check a v3 WRITE and READ claim against the record	21 hours ago
suricatactl	rust: hoist regex dependency into workspace	6 days ago
suricatasc	rust: hoist serde_json dependency into workspace	6 days ago
sys	rust: inherit common package metadata from workspace	6 days ago
.gitignore	…
Cargo.lock.in	rust: update zstd	2 days ago
Cargo.toml.in	rust: update zstd	2 days ago
Makefile.am	rust/derive: add Makefile for Cargo.toml regeneration	6 days ago
cbindgen.toml	http2: split transaction state machines	4 months ago
rustfmt.toml	…