This commit simply removes an unused Python 3.7 CI Docker file and cleans up a leftover dependency for Python 3.6. There is no security issue here—it's routine housekeeping.
This commit simply updates web links and folder names in HWI's build scripts and documentation to match Ledger's renamed GitHub repositories. It does not change any wallet code, cryptography, or user-facing behavior. There is no security i…
This change makes the hardware-wallet interface library stricter when reading PSBT (Partially Signed Bitcoin Transaction) files. It now rejects locktime values that don't follow Bitcoin's rules: a time-based locktime must be at least 500,0…
Input validation added to PSBT deserializationEnforcement of Bitcoin locktime semantics boundary (500000000)New negative test cases for invalid locktime combinations
This commit fixes a parsing bug in the way the Hardware Wallet Interface (HWI) reads Bitcoin transaction files called PSBTs. PSBTs come in two versions, v0 and v2, and each version has its own allowed fields. The code was accidentally acce…
PSBT version confusion: v2-only fields accepted in v0 PSBTPotential transaction malleability / unintended signature scopeParsing strictness fix with new negative test vectors
This change fixes a subtle parsing bug in how the wallet software reads PSBT (Partially Signed Bitcoin Transaction) files. Previously, the code could not tell the difference between a PSBT that genuinely contained an unsigned transaction w…
Ambiguous sentinel value used as a proxy for key presencePSBT version-specific validation bypass possibleNew test vector added for empty unsigned transaction edge case
This commit fixes a bug in how the wallet interface reads the unsigned transaction embedded inside a PSBT (Partially Signed Bitcoin Transaction). Previously, the parser tried to auto-detect whether the transaction included witness data, wh…
PSBT global unsigned transaction parsing now strictly enforces non-witness serializationNew deserialize_without_witness method removes witness-marker auto-detectionAdds explicit PSBTSerializationError for invalid or trailing bytes in the unsigned tx field
This commit is a routine release-management update. It adds signed build assertions for three new BitBox02 firmware versions (9.26.2, 9.26.3, 9.26.4) and updates the release documentation and build helper script. The build script now delet…
No firmware source code is modifiedNo cryptographic primitives or protocols are changedNo bug fixes or vulnerability mitigations are present in the diff
This commit only deletes an incorrect explanatory comment. The actual code behavior does not change at all. It is a documentation cleanup, not a security fix.
This commit only reformats existing Zcash PCZT code—adjusting line breaks, indentation, and whitespace. No logic, behavior, or security checks were changed.
This commit simply removes one person (Pieter Wuille) from the list of security contacts in the project's SECURITY.md file. It is an administrative change to the documented contact list and does not alter any code, fix any bug, or change a…
This commit is a routine developer tooling change. It turns on stricter Python type checking (Pyright) for the emulator script and some test helper scripts, and makes small code adjustments so those files pass the new checks. There is no c…
This commit only changes test infrastructure. It enables extra logging output during automated testing so developers can see more detail when running tests. There is no change to the actual Trezor firmware or wallet security code, and no s…
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.