<?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 PeteMahon.net</title><link>https://petemahon.net/tags/bitwarden/</link><description>Recent content in Bitwarden on PeteMahon.net</description><generator>Hugo</generator><language>en-us</language><copyright>&lt;a href="https://creativecommons.org/licenses/by-nc/4.0/" target="_blank" rel="noopener"&gt;CC BY-NC 4.0&lt;/a&gt;</copyright><lastBuildDate>Thu, 30 Apr 2026 09:30:00 +0400</lastBuildDate><atom:link href="https://petemahon.net/tags/bitwarden/index.xml" rel="self" type="application/rss+xml"/><item><title>Two Vendors, Two Keys: Keeping Passwords Outside Proton</title><link>https://petemahon.net/posts/proton-pass-vs-bitwarden/</link><pubDate>Thu, 30 Apr 2026 09:30:00 +0400</pubDate><guid>https://petemahon.net/posts/proton-pass-vs-bitwarden/</guid><description>&lt;p&gt;This series has been about moving from Microsoft to Proton. One thing didn&amp;rsquo;t move, and was never going to: my password manager. Bitwarden was already in place across my household before any of this began, and it stayed where it was while the rest of my stack got rebuilt.&lt;/p&gt;
&lt;p&gt;Proton has its own password manager, Proton Pass; on the face of it, consolidating onto it would have been the consistent move. I didn&amp;rsquo;t seriously consider it and this post is about &lt;em&gt;why&lt;/em&gt;. It has very little to do with Pass itself and quite a lot to do with deliberately not keeping all the keys to my life under a single login.&lt;/p&gt;</description></item></channel></rss>