mirror of
https://github.com/rosenpass/rosenpass.git
synced 2026-02-27 22:13:12 -08:00
9824db4f09
The new secret memory pool was causing CI failures in the fuzzing code, due to the fuzzer compiling its binaries with memory sanitizer support. https://doc.rust-lang.org/beta/unstable-book/compiler-flags/sanitizer.html Using lazy_static was – intentionally – introducing a memory leak, but the LeakSanitizer detected this and raised an error. Now by using thread_local we are calling the destructors and so – while still being a memory leak in practice – the LeakSanitizer no longer detects this behaviour as an error. Alternatively we could have used a known-leaks list with the leak-sanitizer, but this would have increased the complexity of the build setup. Finally, this was likely triggered with the migration to memsec, because libsodium circumvents the malloc/free calls, relying on direct calls to MMAP.
26 lines
793 B
TOML
26 lines
793 B
TOML
[package]
|
|
name = "rosenpass-secret-memory"
|
|
version = "0.1.0"
|
|
authors = ["Karolin Varner <karo@cupdev.net>", "wucke13 <wucke13@gmail.com>"]
|
|
edition = "2021"
|
|
license = "MIT OR Apache-2.0"
|
|
description = "Rosenpass internal utilities for storing secrets in memory"
|
|
homepage = "https://rosenpass.eu/"
|
|
repository = "https://github.com/rosenpass/rosenpass"
|
|
readme = "readme.md"
|
|
|
|
[dependencies]
|
|
anyhow = { workspace = true }
|
|
rosenpass-to = { workspace = true }
|
|
rosenpass-sodium = { workspace = true }
|
|
rosenpass-util = { workspace = true }
|
|
libsodium-sys-stable = { workspace = true }
|
|
zeroize = { workspace = true }
|
|
rand = { workspace = true }
|
|
memsec = { workspace = true }
|
|
allocator-api2 = { workspace = true }
|
|
log = { workspace = true }
|
|
|
|
[dev-dependencies]
|
|
allocator-api2-tests = { workspace = true }
|