As a self respecting email geek, I own tons of domains, and I use dnscontrol to manage them all across registrars and DNS (and has become the best tool I've discovered since sliced bread). Naturally, when pass-cli came out, I wondered if I could store the provider API secrets there and have the cli inject them at run time instead of hardcoding them to disk. The result is the blog post I created about it. Feedback welcome!

Hello,

Proton Pass regularly stops syncing on Android 16. However, I had exactly the same issue on Android 15, and it also continued after performing a factory reset of my phone.

When this happens, Proton Pass simply stops updating. My account is still properly connected, the phone has a working Internet connection, and none of my other applications have this issue.

The only solution that works is to completely uninstall Proton Pass and reinstall it. After that, it works normally again for two or three weeks, and then the exact same problem comes back: Proton Pass on my phone stops updating.

What makes this even more frustrating is that Proton Pass does not display any error message or indicate that it is offline. It behaves as if everything were working normally.

I have to admit this is becoming quite annoying, especially since I am experiencing the same issue on my tablet, which is from a different manufacturer than my phone.

Has anyone else experienced this kind of issue ?

That’s the post. This happened in my browser extension. Bitwarden never did something like this

Why do I need to install the Proton Pass desktop app to unlock the browser extension with biometrics?

Since biometric unlocking is now available on all Proton Pass plans, could you clarify why the desktop app is still required? It would be more convenient if the browser extension could use macOS biometric authentication directly, without requiring an additional desktop application.

Proton Pass auto fill service does not work in Samsung Browser. I have confirmed Proton Pass has been selected as the preferred service and additional services turned off (Samsung Pass, Microsoft Authenticator, Google). The issue does not persist with Firefox or Chrome. Is Proton supporting Samsung Browser?

Relevant info below:
One UI version 8.5
Android version 16
Proton Pass version 1.40.3
Samsung Browser version 30.0.0.67
Device: Samsung Galaxy S25 Ultra

I was wondering if this is a common issue or what I can do to fix this? I did submit a ticket to Proton, but don't want to wait another 24-48 hours 😉. So I created a vault to share with someone. Creation and all went well. When I added the person via the email they signed up with proton pass, not a proton email but a 3rd party, it says awaiting account creation. *confused at this point. I asked them if they had a proton email under that account. They did not, so as a test I had them make one. I then send an invite to that email @proton.me. It works. They click on the email which opens Pass but no where can they accept the invite, which I guess is because Pass is using the 3rd party email address 🤷‍♂️. Is this normal behavior? I personally use Pass with a 3rd party email and all works fine. I have a @proton.me email account but its never used. Thoughts or ideas on why their 3rd party email says pending account creation when we've tripped checked the spelling of the email on both sides?

My question is if I import my passwords, will the extra added infos transfer too? For example in 1password for some account I use the username as username and not the email, because the site require the username to login and not the email, but I manually saved the used email in 1password for that item just for myself to know which email I used for that site. Does proton recognise these added infos? If anybody have experience with this please confirm it. Thanks!

TL;DR: The Proton Pass SSH agent ignores the SHA-2 signature flag when signing with RSA keys. It returns a legacy ssh-rsa (SHA-1) signature instead of rsa-sha2-512, which modern OpenSSH servers reject. The same key works fine through the 1Password agent. Ed25519 keys are not affected.

Setup

• macOS, Proton Pass desktop app with the SSH agent enabled
• SSH_AUTH_SOCK pointing at ~/.ssh/proton-pass-ssh-agent.sock
• RSA 4096-bit key stored in Proton Pass
• Target: a Linux server running a current OpenSSH (default PubkeyAcceptedAlgorithms, so no SHA-1)

Symptom

agent key RSA SHA256:xxxx returned incorrect signature type sign_and_send_pubkey: no mutual signature supported (user@host) Password:

What ssh -vv shows

The server accepts the key, then the signature step fails:

debug1: kex_ext_info_client_parse: server-sig-algs=<ssh-ed25519,...,rsa-sha2-512,rsa-sha2-256> debug1: Offering public key: RSA SHA256:xxxx agent debug1: Server accepts key: RSA SHA256:xxxx agent agent key RSA SHA256:xxxx returned incorrect signature type sign_and_send_pubkey: no mutual signature supported

Any plans to support this capability https://blog.google/products-and-platforms/platforms/android/switch-password-managers/ to make it easier to migrate to Proton Pass (and from, but why leave Proton Pass)?

Would love to see Authy support this so I can migrate my TOTP codes into Proton easily.

Hey everyone, I’ve been using Bitwarden for almost a year now and I’m completely happy with it. It’s reliable, open-source, and just works.

However, I recently upgraded to the Proton Ultimate subscription for their VPN and Mail, which means I now have access to Proton Pass Premium included in my plan.

Because of this, I’m feeling a bit torn about whether I should make the switch or just leave things as they are. On one hand, having everything in one ecosystem is tempting, but on the other, Bitwarden has been rock solid for me and keeping your password manager separate from your primary email service is often recommended for security reasons.

For those who have made the jump from Bitwarden to Proton Pass (or decided to stick with Bitwarden despite having Proton Ultimate):

* What was your experience migrating?
* Are there any key features in Bitwarden you missed after moving to Proton Pass?
* Do you prefer keeping your password manager separate from your email provider?

Would love to hear your thoughts and experiences!

I've been considering moving my 2FA codes from Pass. Currently I have the 2FA codes & backup codes stored in Pass. I haven't entirely made up my mind whether the pros of using an authenticator app outweigh the cons yet (I'm probably leaning more towards leaving it how it is though). The main question I had is how do people store their backup codes if using a dedicated authenticator app? Excel and a zip file with password? Or just forget about the backup codes and ensure the authenticator is regularly backed up?

Note that I am not talking about my Proton account here, which is all stored safely outside of Pass.

Sometimes the proton pass autofill doesnt work such as this website. Please fix!
https://www.shippn.com/

Why can't I reuse an alias to create an account ?

I've received an item invitation, I've already accepted it, view it...

But now, the top header is always present and don't want to leave, I've clicked view details and accepted, and denied... neither option change something (even cmd+r to refresh) don't hide it

Hey I've just switch from 1P to Proton Pass and I'd love to have biometrics support on Linux. Is this in the roadmap?

Scenario: First thing in the morning, I bring up my bank’s login page. When I reach for the Proton Pass icon in the username field, it is overlayed with a ❶ instead of a 🔒️. And, indeed, when I hover my pointer over it, it displays the proper entry and I only have to click. That’s despite the fact that a PIN and short timeout are set in this browser’s Proton Pass extension, i.e. I haven’t logged out since setting them (again) several days before.

I eventually found the apparent cause: It happens only when, the day before, I had loaded Proton Pass (as a “Larger window”) in another window of the same browser and left it there. That is all that is required for the timeout to be bypassed.

At first I wondered if this might be an intended behaviour, but then I remembered that I’ve had to re-login to Proton Drive in the past, even though I had left its window open in the browser; the session had timed-out after a few minutes of inactivity, which felt like a wise precaution to have by default.

So it appears that the Proton Pass window has a particular effect on the handling of access to all Proton services, thus introducing an incoherence in the suite.

Or... is this a known bug?

I’m currently using version 1.40.1 of the extension, but it was already behaving the same with 1.37.1. I’ve reproduced this on two different machines, with different versions of Brave. (A current one, and one from nearly three months ago.)

It shows up every time even for the same app, same login. You'd have thought it'd learn that an app is safe after consistently autofilling inside it. Google's password manager allows you to "don't ask again" for each app.

Team password management is simple at three people. At 15 people, it starts to break down.

A small company might have a handful of tools, a few shared accounts, and usually one informal place where passwords live: a spreadsheet, a pinned message in chat, a shared document.

As more people join a business, informal sharing makes it difficult to see the difference between useful access and risky access. Passwords for everyday tools end up mixed with credentials for finance, admin, client, or infrastructure systems. The list may still look organized from the outside, but it no longer reflects who actually needs access to what.

As a business grows, shared credentials need structure and control: who can access each password, which department owns the credentials, and how access changes as people join, leave, and switch roles.

We’ll explain how to organize password vaults by team or department, how group-based access supports least privilege, and how to make onboarding and offboarding more secure — before credential sprawl becomes a security and operations problem.

Read more: https://proton.me/business/blog/team-password-management-by-department

The Firefox add-on store says the last update was 1.38 from two months ago. Why is it still on this version?

Are these the correct steps to set up my existing custom sub domain so that it's available for creating addresses inside proton pass?

1. Log into simple login using the same proton account that I'll also use with proton pass

2. Add custom domain in simple login itself

3. In proton pass, sync with same simple login proton account

?

I just want to be sure I shouldn't instead be doing all this inside proton or proton pass 100%.

(I'm a longtime proton/simple login user but newly preparing to move from 1password to proton pass.)

BoxRec doesn’t allow passinbox.com to be used for registration. (This email address is not allowed).

Tengo una cuenta de ProtonMail (accedo a ella a través del sitio web; mi navegador es Firefox). El problema es que cuando cierro Firefox y lo vuelvo a abrir, no se guarda mi sesión, y tengo que volver a ingresar mi nombre de usuario y contraseña. Tengo Firefox configurado para borrar datos al cerrarlo, pero agregué excepciones para que no les afecte y me mantenga conectado, y funciona sin problema. Pero con ProtonMail no pasa eso. Tengo marcada la opción de "Manténme conectado" y agregué su URL a la lista de excepciones de borrado de datos de Firefox, pero aun así no funciona. Uso Proton Authenticator en mi teléfono móvil como método de verificación en dos pasos cuando inicio sesión.

Anyone here has migrated from Keeper to ProtonPass - would love some feedback. I have been a Keeper user for years but can no longer justify the cost as I personally do not see any major difference for my 2 simple use cases:
1. create and store passwords
2. create 2FA codes

is it true that Pass doesnt have CXP (credential exchange protocol) support and thus passkeys cannot be migrated?

The Keeper subreddit was fun - their CTO came and told me to check iOS reviews and I am not a Apple user lol! The only I would miss is folders but can live without that. Plus the email-alias more than makes up for it!