24 Commits

Author SHA1 Message Date
x
9785777642 chore: Update copyright license year
Happy 2026!
2026-01-01 11:40:45 +00:00
x
add9bb596c chore: Update crate dependencies 2025-12-25 12:22:56 +00:00
x
aa537b9e4b chore: Update crate dependencies 2025-11-24 12:12:14 +02:00
parazyd
fda2a84034 chore: Update dependencies 2025-08-05 09:41:05 +02:00
parazyd
c040d9c00f chore: Update crate dependencies 2025-04-15 10:49:43 +02:00
parazyd
604f443fd1 chore: Update license header year 2025-01-24 10:36:02 +01:00
parazyd
b5d7c52191 chore: Update crate dependencies 2025-01-21 14:21:32 +01:00
parazyd
242fe81658 chore: Update crate dependencies 2024-10-01 14:15:03 +02:00
parazyd
27fd3785f8 chore: Update crate dependencies and CI Rust version 2024-07-09 12:20:06 +02:00
foo
4eba00236d clippy: add suggested clippy lints to top-level Cargo.toml and enable
clippy linting at the workspace level for all crates

Configure all workspaces to use lints from the top-level Cargo.toml
  file
Add example lints that the project could configure to improve security
  and reliability.
Configure lints to warn level. Using deny level makes other binaries
fail to compile if even one of them has a failure.
No lints are added in this commit. Future changes can enable and fix
lints
2024-06-09 10:35:09 -04:00
parazyd
80d103a2ba chore: Update crate dependencies 2024-06-04 10:24:28 +02:00
parazyd
2e37330d0d chore: Update crate dependencies 2024-05-27 15:29:58 +02:00
parazyd
0de97d0db3 chore: Update crate dependencies 2024-03-05 08:47:43 +01:00
parazyd
0e6f51e895 chore: Update copyright year in license headers 2024-01-16 13:07:22 +01:00
parazyd
f188c2bb05 chore: Update crate dependencies 2023-11-09 14:20:57 +01:00
parazyd
b61127af9a chore: Update crate dependencies 2023-10-27 09:02:18 +02:00
y
2d41e54f14 fuzz: move all artifacts into regressions
Merge the libfuzzer and honggfuzz saved crash inputs into a shared
folder in fuzz/regressions

Add relevant entries to .gitignore
2023-09-19 16:13:50 -04:00
y
e7a7f6d02d fuzz: add regressions/ folder; improve READMEs 2023-09-19 16:09:22 -04:00
y
aaed928482 fuzz: cleanup zkas-compile harness in honggfuzz 2023-09-19 14:44:03 -04:00
y
c669ba4696 fuzz: fix old code comment in script 2023-09-16 23:00:24 +00:00
y
f9ed0b825c fuzz: add script to generate .zk file corpus 2023-09-16 23:00:24 +00:00
y
9d97aebf50 fuzz: Add fuzz harness for zkas compilation
Create a fuzz harness to test the ./zkas binary compilation process. The
whole pipeline is tested: Lexer, Parser, Compiler, Analyzer. This is
performed by copying the relevant code from bin/zkas/src/main.rs.

Testing the entire pipeline like this is not very efficient in terms of
fuzzing cycles but on the other hand it is a quick-and-dirty way to find
results. It also benefits from testing the actual inputs to the binary
in the way it's expecting, rather than checking each of the components
in a piecemeal way using interfaces that aren't expected to be exposed
anyway.
2023-09-16 23:00:24 +00:00
y
e23a5e9ee5 fuzz: Add differential fuzzing for BTC VarInt
DarkFi's VarInt struct is meant to be equivalent to the one used by BTC.
Most of the source code is extremeley similar. This commit adds very
basic tests to ensure equivalence between DarkFi's implementation and
the one used by the BTC crate.
The tests included here are quite basic. Future work can expand on
the testing done on the deserialized values.
This harness can also be used as as guide or template for future
differential fuzzing.
2023-09-06 10:57:28 +00:00
greptile
d9d918b884 fuzz: Add honggfuzz (#206)
* fuzz: Add honggfuzz

- Added honggfuzz in fuzz2/ (alongside libfuzzer in fuzz/)
- Created convenience script for fuzzing binary decoder
- Created a script to convert inputs that cause crashes into arrays so
  that they can be used in unit tests

* Create honggfuzz as subdirectory of fuzz/

- Reorg so that honggfuzz is under fuzz/ instead of in a separate
  sibling-level directory fuzz2
- Update fuzz/README.md to make it explicit that it covers libfuzzer

Note: `cargo fuzz`/libfuzzer seems to insist that its folder exists at
`$REPO/fuzz/` so that's the reason for this particular folder structure.

---------

Co-authored-by: y <y>
2023-09-04 16:42:34 +00:00