Skip to content

Commit 0a415d2

Browse files
Remove the shared_cache fuzz target
1 parent e81577f commit 0a415d2

17 files changed

Lines changed: 50 additions & 315 deletions

‎README.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -22,4 +22,4 @@ SQLite3MC is MIT licensed. The amalgamation also carries public-domain code (SQL
2222

2323
A daily workflow in the [repository](https://github.com/LucaCappelletti94/sqlite3mc-src) opens a pull request for each new SQLite3MC release, taking the archive's checksum only from the release's Sigstore-signed `SHA256SUMS`. CI re-runs `upgrade.sh`, which checks that signature again before trusting the pinned checksum, to prove the vendored bytes match the pinned release. It also compiles the packaged sources natively and through `sqlite-wasm-rs`, and checks that each build opens the other's files in every cipher, under Node and in headless Chrome and Firefox, on OPFS too.
2424

25-
CI also runs SQLite3MC's own tests, a rekey of every cipher and SQLite's TCL suite through the shipped amalgamation, once plainly and once under the address and undefined-behaviour sanitizers, with every expected failure named and explained. Six fuzz targets in `fuzz/` run on every pull request and daily through `ClusterFuzzLite`: a self-consistency check across the six native cipher schemes, and dedicated targets for rekeying, `journal_mode=WAL`, `ATTACH DATABASE`, the `sqlite3_backup_*` API, and shared-cache mode.
25+
CI also runs SQLite3MC's own tests, a rekey of every cipher and SQLite's TCL suite through the shipped amalgamation, once plainly and once under the address and undefined-behaviour sanitizers, with every expected failure named and explained. Five fuzz targets in `fuzz/` run on every pull request and daily through `ClusterFuzzLite`: a self-consistency check across the six native cipher schemes, and dedicated targets for rekeying, `journal_mode=WAL`, `ATTACH DATABASE` and the `sqlite3_backup_*` API. Shared-cache mode is left out, since SQLite discourages it and SQLite3MC supports it only as legacy ([#290](https://github.com/utelle/SQLite3MultipleCiphers/issues/290)).

‎fuzz/Cargo.toml‎

Lines changed: 1 addition & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ name = "sqlite3mc-src-fuzz"
33
version = "0.0.0"
44
edition = "2021"
55
publish = false
6-
description = "Fuzzing SQLite3MC's own cipher schemes for self-consistency, its rekey support, its WAL journal mode, its ATTACH DATABASE support, its backup API, and its shared-cache mode"
6+
description = "Fuzzing SQLite3MC's own cipher schemes for self-consistency, its rekey support, its WAL journal mode, its ATTACH DATABASE support, and its backup API"
77

88
[package.metadata]
99
cargo-fuzz = true
@@ -51,13 +51,6 @@ test = false
5151
doc = false
5252
bench = false
5353

54-
[[bin]]
55-
name = "shared_cache"
56-
path = "fuzz_targets/shared_cache.rs"
57-
test = false
58-
doc = false
59-
bench = false
60-
6154
# The crate's table, minus unsafe_code (FFI) and missing_docs and cargo (never published).
6255
[lints.rust]
6356
rust_2018_idioms = { level = "warn", priority = -1 }
-64 Bytes
Binary file not shown.
-656 Bytes
Binary file not shown.
-323 Bytes
Binary file not shown.

‎fuzz/corpus/shared_cache/no-siblings‎

Lines changed: 0 additions & 2 deletions
This file was deleted.
-212 Bytes
Binary file not shown.
-1.54 KB
Binary file not shown.
-804 Bytes
Binary file not shown.

‎fuzz/examples/gen_shared_cache_seeds.rs‎

Lines changed: 0 additions & 81 deletions
This file was deleted.

0 commit comments

Comments
 (0)