<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Bitwarden on Linux Colorado</title><link>https://www.linuxcolorado.com/tags/bitwarden/</link><description>Recent content in Bitwarden on Linux Colorado</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Sat, 31 Oct 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://www.linuxcolorado.com/tags/bitwarden/index.xml" rel="self" type="application/rss+xml"/><item><title>Moving 545 Passwords from Bitwarden's Cloud to Vaultwarden: the YubiKey Detour and the Count That Lied</title><link>https://www.linuxcolorado.com/post/2026-10-31-bitwarden-to-vaultwarden-migration/</link><pubDate>Sat, 31 Oct 2026 00:00:00 +0000</pubDate><guid>https://www.linuxcolorado.com/post/2026-10-31-bitwarden-to-vaultwarden-migration/</guid><description>&lt;p&gt;For years I kept my password vault in Bitwarden&amp;rsquo;s cloud on a Premium subscription. It worked, it was cheap, and the clients were lovely. Then Bitwarden&amp;rsquo;s licensing direction this year gave me the nudge, on top of a reason I&amp;rsquo;d already settled on: I wanted the vault on hardware I own, behind my own TLS and my own backups.&lt;/p&gt;
&lt;p&gt;The clients stay exactly the same. Vaultwarden speaks the Bitwarden API, so the browser extensions, desktop app and phone apps just get a new server URL — the change is where the bytes live, not how I touch them.&lt;/p&gt;
&lt;p&gt;What follows is the honest version: a migration designed so my master password never passed through the AI assistant I do my homelab work with, a YubiKey detour of my own making, and three item counts for one vault that disagreed until I learned which to trust.&lt;/p&gt;</description></item></channel></rss>