Avinash Sajjanshetty dc3d1fa36d Use the SQLite header as associated data for protection ...

against tampering and corruption.

Previously, we did not use the first 100 bytes in encryption
machinery. This patch changes that and uses that data as
associated data. So in case the header is corrupted or
tampered with, the decryption will fail.

2025-09-27 17:34:51 +05:30

..

btree.rs

core/storage: Display page category for rowid integrity check failure

2025-09-26 18:25:49 +03:00

buffer_pool.rs

core: Use sequential consistency for atomics by default

2025-09-18 13:38:13 +03:00

checksum.rs

core: Wrap Connection::pager in RwLock

2025-09-22 17:02:08 +03:00

database.rs

remove some unnecessary unsafe impls

2025-09-21 13:29:59 -03:00

encryption.rs

Use the SQLite header as associated data for protection

2025-09-27 17:34:51 +05:30

mod.rs

Add checksum module

2025-09-13 11:00:37 +05:30

page_cache.rs

core: Use sequential consistency for atomics by default

2025-09-18 13:38:13 +03:00

pager.rs

core: Wrap Connection::is_nested_stmt in AtomicBool

2025-09-24 19:30:31 +03:00

slot_bitmap.rs

Rename page -> slot for arenas + buffer pool

2025-08-12 11:36:49 -04:00

sqlite3_ondisk.rs

core: Wrap Connection::page_size with AtomicU16

2025-09-24 09:12:46 +03:00

state_machines.rs

refactor/idx_insert: move seeking to VDBE instead of BTreeCursor

2025-08-19 19:04:42 +03:00

wal.rs

core: Wrap Connection::pager in RwLock

2025-09-22 17:02:08 +03:00