This is a small follow-up patch to a security check inside Sparrow Wallet's database loader. The change tightens how the app scans a wallet file's internal database schema for dangerous commands that could let an attacker run code or link …
Hardening of DDL injection filter in wallet file loaderNew identifier-stripping step to prevent regex evasion via quoted table namesBroadened blacklist pattern for H2-specific dangerous objects (TRIGGER, ALIAS, LINKED TABLE)
This commit only updates outdated web links in documentation and code comments. It does not change any program logic, network behavior, or security checks. There is no security issue here.
This commit is purely a test-data update for Trezor's Ethereum 'clear signing' feature. It removes old built-in test fixtures and adds new externally-supplied token/chain definition files so the test suite can exercise how the device handl…
No production code changesTest-only fixture addition and removalExternal definition loading helpers are test scaffolding
This commit removes built-in, hard-coded display rules for the LI.FI swap/bridge protocol from Trezor's Ethereum 'clear signing' feature. It is a feature cleanup, not a fix for a code vulnerability. The change means Trezor will no longer a…
Removal of hard-coded protocol-specific display definitionsNo changes to transaction parsing, signing, or access-control codeTest fixtures migrated to external-definitions test path
This commit updates the secp256k1 cryptographic library inside Bitcoin Core to a newer version. The main change is adding support for a new optional feature called 'Silent Payments' (BIP352), which is a privacy-enhancing way to receive Bit…
New cryptographic module added (Silent Payments / BIP352)Field-element equality check magnitude bound corrected from 31 to 30X-only public key even-Y invariant enforced in extrakeys module
This commit is a routine API cleanup: it makes a few Bitcoin merkle-root functions accept a broader range of input types (generic iterators and borrowed transactions) instead of only slices or exact iterator types. There is no security bug…
This is a minor code cleanup that removes an unnecessary copy of the first transaction in a Bitcoin block validation routine. It does not change behavior, fix a bug, or address any security issue.
This is a small Cargo.toml configuration change that forwards feature flags from the taproot-primitives crate to its internal bitcoin-crypto dependency. It does not change any executable code, fix a bug, or alter behavior under current fea…
No source-code changesNo memory-safety, cryptographic, or input-validation changesNo bug fix or vulnerability remediation described in commit message
This commit simply switches two software building blocks (called 'crates') from a development Git snapshot to a published release version (1.0.8) on the official Rust package registry. The change itself does not add, remove, or modify any …
This commit is a routine cleanup of leftover references to old test scripts in configuration files. It removes stale entries from a GitHub labeler config, .gitignore, and a label generator, deletes an unused helper script, and inlines its …
This commit only adds documentation comments to an existing Rust function. It explains what the function returns and how that return value can be reused. No code behavior was changed, so there is no security impact.
This commit adds a new diagnostic command to Trezor's production-test firmware that simply reports the device's internal model name. It does not change normal user firmware, does not handle secrets, and does not appear to introduce any sec…
A quiet fix may be responsible caution—or it may leave users unaware that their assets were ever at risk. CommitWatch preserves the evidence, adds context, and tracks whether vendors disclose, acknowledge, and learn.