AI-generated analysisPublished automatically and not human-verified. Validated context appears in community notes below.
← Watch feed
Low 29 Bitcoin

standalone encrypted backups for Secure Notes & Passwords

Public commit record

What the developer wrote

Authored by scgbckbone

50/100 · Thin
standalone encrypted backups for Secure Notes & Passwords
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
The short version

What changed, and why it matters

This commit adds a new feature to the COLDCARD firmware: encrypted backups for Secure Notes & Passwords. Previously, exporting notes and passwords to a microSD card produced an unencrypted JSON file. Now the device can encrypt that export using the same 7z/AES backup encryption used for full wallet backups. The change also refactors the existing backup password code so it can be reused for both full-device and notes-only backups. A small, unrelated fix in message signing changes a logical AND to an OR when deciding whether tab/newline characters are allowed in signed text. There is no vendor disclosure of a security vulnerability, and the commit is framed as a feature addition.

Recommended action

Review the refactored backup encryption helpers for correct password handling and ensure the new .json inner-extension check does not weaken backup file validation. Specifically verify that the auth.py change from `is_json and allow_tab_nl` to `is_json or allow_tab_nl` is intentional and does not introduce unintended character acceptance in message signing. Treat this commit as a feature patch rather than an emergency security fix unless additional context emerges.

Security signals we found

01

New encryption feature for previously cleartext notes/password exports

02

Refactoring of backup password and 7z encryption code into reusable helpers

03

Addition of inner_ext parameter to backup decryption to support .json payloads

04

Logic change in message-signing text validation (AND to OR)

05

No vendor security disclosure or CVE references present in commit materials

Risk score

Why this scored 29/100

Our methodology →
Potential impact 5/30
Exploitability 5/25
Stealth signal 5/15
Affected reach 5/15
Confidence 6/10
Evidence quality 3/5
Human-validated context

Community notes

Notes can correct, qualify, or add evidence to the AI analysis. Every note shown here has been validated by a human moderator.

No validated notes yet.

The AI analysis stands alone for now. Submit a note if you can add evidence or important context.