s.c.
My feedback
104 results found
-
94 votes
An error occurred while saving the comment s.c.
supported this idea
·
-
14 votess.c.
supported this idea
·
-
40 votess.c.
supported this idea
·
-
3 votes
An error occurred while saving the comment s.c.
commented
Exactly... This is an issue on macOS too. If a new biometric is registered in the macOS system (e.g. new Finger registered for Touch ID), Proton Pass should automatically lock, refuse to accept Touch ID for unlock and require the Proton Pass Account password or extra password before Biometrics can be used again. The macOS Proton Pass app should utilise Keychain Key Invalidation at the Secure Enclave level to cryptographically invalidate the encryption key used to protect the Proton Pass app's local database. This uses the access control flag .biometryCurrentSet. How it should work: This flag pairs the Keychain item strictly to the biometric configuration present at the exact moment the item was saved.The result: If a new fingerprint is registered, the Secure Enclave will completely refuse to release or decrypt that Keychain item. The Proton Pass app will receive an authentication error when trying to fetch the key, naturally forcing the user back to entering their Proton Account Password or Proton Pass Extra Password (not macOS login password).
We should implement hardware and software-level controls to bind the application vault token strictly to the exact biometric compilation present at initialization:
Strict Policy Enforcement:
Force `LAContext` execution parameters to point exclusively to `.deviceOwnerAuthenticationWithBiometrics` rather than allowing general device passcodes to qualify as validation criteria.Hardware Token Invalidation:
Leverage Secure Enclave isolation during `SecAccessControlCreateWithFlags` initialization by assigning `.biometryCurrentSet` flags to stored items. This instructs the hardware to break and invalidate access tokens the moment any alterations to the host fingerprint database are registered.Proactive State Tracking:
Read and persist `context.evaluatedPolicyDomainState` signatures alongside the validation configuration. Compare this state before invoking validation to gracefully intercept altered biometric configurations, dropping authorization flows down to the primary Master Password route while providing clear explanatory UI logs to the user.An error occurred while saving the comment s.c.
commented
This is super important and needs to be fixed ASAP. Also an issue on macOS too.
s.c.
supported this idea
·
-
16 votes
An error occurred while saving the comment s.c.
commented
100%. Can't believe this has been open for almost a year without being fixed. It's a major security weakness.
When the Security Settings > Unlock with option is set to "Biometrics", the Proton Pass app should not offer to use "Password" as a fallback. If Touch ID doesn't work or fails, it should require the Proton Pass Account or Extra Password to unlock to Proton Pass, it should not fall back to the macOS User Account password to permit access. The Proton Pass app should not use .deviceOwnerAuthentication as a policy to avoid macOS falling back to the macOS login password instead of the user’s Proton Account Password or Proton Pass Extra Password. Instead the app should utilise .deviceOwnerAuthenticationWithBiometrics.
s.c.
supported this idea
·
-
9 votess.c.
supported this idea
·
-
19 votess.c.
supported this idea
·
-
98 votes
An error occurred while saving the comment s.c.
commented
This feature was removed (with no warning) when they moved their iOS and ipadOS app to the next Drive SDK. It needs to be reinstated as soon as possible. The Proton drive app is useless without it.
s.c.
supported this idea
·
-
210 votes
We will create a dedicated iPad interface in the future.
An error occurred while saving the comment s.c.
commented
This has been planned since 2016!?! Come on Proton team, we need a proper native iPad app that takes full advantage of the screen real estate available on the iPad. Reading pane, permanent side bar, full screen mode, etc.
s.c.
supported this idea
·
-
6 votess.c.
supported this idea
·
-
4 votess.c.
supported this idea
·
-
4 votess.c.
supported this idea
·
-
26 votess.c.
supported this idea
·
-
3 votes
An error occurred while saving the comment s.c.
commented
Agreed. Give us back this option. It would be a great stop gap until you add native macOS Autofill to the macOS Proton Pass app.
s.c.
supported this idea
·
-
1 votes.c.
shared this idea
·
-
18 votess.c.
supported this idea
·
-
3 votess.c.
supported this idea
·
-
3 votess.c.
supported this idea
·
-
13 votess.c.
supported this idea
·
-
3 votess.c.
supported this idea
·
Please please please add this very basic feature.