Douglas Morris
My feedback
3 results found
-
7 votes
An error occurred while saving the comment -
32 votes
An error occurred while saving the comment Good evening all,
I was sitting here thinking this evening as on a new tablet I picked up proton pass is working inconsistently as always and appearing at best half the time the keyboard is on an app that requires a login even despite all settings being in their most optimal modes that perhaps the solution isn't trying to make proton pass work better with various keyboards but perhaps proton needs to make their own keyboard app that perhaps is able to directly integrate with proton pass. Let's be honest here keyboards have always been a major privacy concern whether it's Google's Microsoft's or someone else's if proton were to provide their own security based keyboard that guaranteed user data protections I think that in and of itself would have great value and probably help eliminate compatibility issues at the same time.
Just a thought anyway I wondered what anybody else thought.
-
6 votes
An error occurred while saving the comment Agreed The behavior seems very inconsistent from app to app despite all settings being validated the way they should be and all battery optimizations for proton pass being disabled I'm not sure what the trigger point is that it's looking for but it definitely has issues on multiple devices on Android with consistency.
I would add to this as an interim goal to at least allow a passkey when it is created to be non-synced as there are times where you do not want them to sync, even if not truly 'Hardware Bound' it allows you to better tie keys to sources. I have no issue with allowing syncing, I am just asking we be allowed to mark a key to not sync off device.
And of course, add support for Hardware Bound Passkeys on devices with TEE (Trusted Execution Environments) or SE (Secure Enclaves) which is most Android and iOS devices in the last few years, If you can do that and ensure it is used with TEE or SE, then you are effectively at Level 2.