open-standards/openpay/crates/op-vault/Cargo.toml
Transaction Science 55110b23b2 openpay: fix op-vault/op-screening rand_core pin (restore workspace resolve)
op-vault and op-screening pinned `rand_core = "0.10"` with the `getrandom`
feature, but rand_core 0.10 removed that feature — so the ENTIRE openpay
workspace failed to resolve (cargo build -p op-core failed identically).
The pin was doubly wrong: both crates use rand_core 0.6's RNG traits —
op-vault via aes-gcm-siv 0.11's `aead::OsRng`, op-screening via
`rand_core::OsRng` + ed25519-dalek's `SigningKey::generate` — both of
which are rand_core 0.6 (already locked at 0.6.4; there was never a 0.10).

Pin both to `rand_core = "0.6"` (which HAS the getrandom feature gating
OsRng). The workspace now resolves; op-vault + op-screening compile and
their 94 tests pass; op-rails-x402 (added in af27203) now builds in the
workspace, not just standalone.

Co-Authored-By: Claude Opus 4.8 <[email protected]>
2026-06-25 18:32:53 -04:00

42 lines
1.7 KiB
TOML

[package]
name = "op-vault"
version.workspace = true
edition.workspace = true
rust-version.workspace = true
license.workspace = true
repository.workspace = true
description = "OpenPay vault. Token-only storage abstraction. PCI DSS 4.0.1 scope-cutter for the rest of the stack."
[dependencies]
op-core = { path = "../op-core", features = ["pci-scope"] }
thiserror = { workspace = true }
serde = { workspace = true }
serde_json = { workspace = true }
time = { workspace = true }
uuid = { workspace = true }
zeroize = { workspace = true }
# AES-256-GCM-SIV is misuse-resistant per RFC 8452 — no catastrophic
# nonce-reuse failure mode. Strictly better than plain AES-GCM for a
# library where the operator wraps our cipher and we can't enforce
# nonce discipline at every callsite. Used only by the in-memory
# reference vault; production deployments use platform-supplied vaults.
aes-gcm-siv = { version = "0.11", default-features = false, features = ["alloc", "aes", "getrandom"], optional = true }
# 0.6 to match aes-gcm-siv 0.11's `aead::OsRng` (its RngCore is rand_core 0.6).
# `getrandom` gates OsRng. (A "0.10" pin never matched usage and lacks the
# getrandom feature, breaking the whole workspace resolve.)
rand_core = { version = "0.6", features = ["getrandom"], optional = true }
[dev-dependencies]
proptest = { workspace = true }
serde_json = { workspace = true }
[features]
# Default ships only the trait + types. No implementation, no crypto.
# Operators bring their own vault (iOS Keychain, Android Keystore, HSM,
# AWS KMS, HashiCorp Vault, etc.).
default = []
# Enables InMemoryVault — AES-256-GCM-SIV-backed reference implementation
# suitable for tests and development. Not PCI-compliant on its own.
in-memory = ["dep:aes-gcm-siv", "dep:rand_core"]