liquidplum
My feedback
10 results found
-
2,432 votes
An error occurred while saving the comment liquidplum
supported this idea
·
-
41 votesliquidplum
supported this idea
·
-
2,276 votes
As mentioned in the previous update on this feature, it is now being edited to be a request for slides.
Please feel free to undo your vote if this is not something you want included in Proton Drive.
liquidplum
supported this idea
·
-
7 votesliquidplum
supported this idea
·
-
20 votesliquidplum
supported this idea
·
-
5 votesliquidplum
supported this idea
·
-
5 votesliquidplum
supported this idea
·
-
9 votesliquidplum
supported this idea
·
-
50 votesliquidplum
supported this idea
·
-
1,343 votes
An error occurred while saving the comment liquidplum
commented
Very important:
-- line spacing
-- paint format featureThe others: not important
liquidplum
supported this idea
·
To second what John Doe said: The Deadlock Problem -- This feature becomes critical when you fully commit to the Proton ecosystem.
Here's the scenario: You follow best security practices and generate a long, complex password for your Proton account. Naturally, you store it in Proton Pass. But now you have a circular dependency. To access Proton Pass, you need your Proton password. To retrieve your Proton password, you need Proton Pass.
This creates a genuine deadlock situation, especially in disaster recovery scenarios where you might be logging in from a new device without any cached sessions.
The workaround today is to either memorize your Proton master password (defeating the purpose of a password manager) or store it somewhere outside of Proton (defeating the purpose of a unified ecosystem).
Allowing Proton Pass to have its own independent unlock method (a separate PIN, passphrase, or biometric) would solve this elegantly. It would let users safely store their Proton credentials inside Proton Pass without risking a lockout.
For users who trust Proton with everything, this is not a convenience feature. It is essential.