<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Security on Bitcoin-Safe - Free &amp; OpenSource software for securely manage your Bitcoin cold storage wallets</title><link>https://pr-76.bitcoin-safe-preview.pages.dev/en/tags/security/</link><description>Recent content in Security on Bitcoin-Safe - Free &amp; OpenSource software for securely manage your Bitcoin cold storage wallets</description><generator>Hugo</generator><language>en-US</language><atom:link href="https://pr-76.bitcoin-safe-preview.pages.dev/en/tags/security/index.xml" rel="self" type="application/rss+xml"/><item><title>Security and reproducibility</title><link>https://pr-76.bitcoin-safe-preview.pages.dev/en/library/reproducibility-and-security/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://pr-76.bitcoin-safe-preview.pages.dev/en/library/reproducibility-and-security/</guid><description>&lt;h3 id="hahahugoshortcode518s0hbhb">
 &lt;a class="header-anchor" href="#hahahugoshortcode518s0hbhb" aria-hidden="true">🔗&lt;/a>
 Security and reproducibility

&lt;/h3>
&lt;p>Bitcoin-Safe follows a high standard for binary security: reproducible builds, signed commits, signed releases, and independent external monitoring.

&lt;br>&lt;/p>
&lt;img src="https://pr-76.bitcoin-safe-preview.pages.dev/en/library/reproducibility-and-security/logo.png" alt="Reproducible build outputs for Bitcoin-Safe" class="img-fluid mb-5 float-end" style="max-width: 500px;">&lt;p>We implemented multiple ways to protect the integrity of the downloads on the website, so the app you download really matches the public source code:&lt;/p>
&lt;ul>
&lt;li>&lt;strong>Reproducible builds&lt;/strong>: Linux &lt;code>deb&lt;/code>, &lt;code>AppImage&lt;/code>, and &lt;code>Flatpak&lt;/code> builds, plus Windows &lt;code>portable exe&lt;/code> and &lt;code>setup exe&lt;/code>, can be reproduced byte-for-byte. If a rebuilt file matches exactly, that is strong evidence that the binary was built from the same source code.&lt;/li>
&lt;li>&lt;strong>Signed repository history&lt;/strong>: the &lt;a href="https://github.com/andreasgriffin/bitcoin-safe/commits/main" target="_blank" rel="noopener">Bitcoin-Safe GitHub repository&lt;/a> publishes verified signed commits, so reviewers can check who authored the code that went into a release.&lt;/li>
&lt;li>&lt;strong>Signed binaries&lt;/strong>: release files are signed with the Bitcoin-Safe &lt;a href="https://keys.openpgp.org/vks/v1/by-fingerprint/2759AA7148568ECCB03B76301D82124B440F612D">public PGP key&lt;/a>, and Windows binaries also follow the &lt;a href="https://pr-76.bitcoin-safe-preview.pages.dev/en/code-signing-policy/">code signing policy&lt;/a>.&lt;/li>
&lt;li>&lt;strong>Independent reproducibility checks&lt;/strong>: &lt;a href="https://walletscrutiny.com/desktop/bitcoin.safe/" target="_blank" rel="noopener">WalletScrutiny&lt;/a> tracks Bitcoin-Safe independently and exposes reproducible-verification status for desktop releases.&lt;/li>
&lt;li>&lt;strong>Ongoing signature monitoring&lt;/strong>: &lt;a href="https://binarywatch.org/" target="_blank" rel="noopener">BinaryWatch&lt;/a> regularly checks Bitcoin-Safe release files and whether their signatures still validate against the Bitcoin-Safe &lt;a href="https://keys.openpgp.org/vks/v1/by-fingerprint/2759AA7148568ECCB03B76301D82124B440F612D">public PGP key&lt;/a>.&lt;/li>
&lt;li>&lt;strong>Update verification&lt;/strong>: Updates are shown in Bitcoin-Safe, and their signature is verified automatically.&lt;/li>
&lt;li>&lt;strong>Protection against malicious servers&lt;/strong>: A malicious server can feed a wallet a conflicting, invalid unconfirmed transaction and trick the user into fee-bumping it, paying the attacker. This class of attack was recently disclosed (&lt;a href="https://github.com/advisories/GHSA-6jp4-8v48-cc5v" target="_blank" rel="noopener">GHSA-6jp4-8v48-cc5v&lt;/a>). Bitcoin-Safe verifies the signatures of its own wallet inputs in synced and locally created transactions, so invalid ones are rejected (&lt;a href="https://github.com/andreasgriffin/bitcoin-safe/pull/873" target="_blank" rel="noopener">PR #873&lt;/a>). Taproot ANYONECANPAY and SINGLE sighashes are not yet covered.&lt;/li>
&lt;/ul>
&lt;p>Taken together, these measures put Bitcoin-Safe in a small group of projects that treat binary security as a first-class part of user safety, not an afterthought.&lt;/p></description></item></channel></rss>