rafacampoamor
My feedback
38 results found
-
334 votes
rafacampoamor
supported this idea
·
-
420 votes
rafacampoamor
supported this idea
·
-
882 votes
rafacampoamor
supported this idea
·
-
215 votes
An error occurred while saving the comment
rafacampoamor
supported this idea
·
-
58 votes
rafacampoamor
supported this idea
·
-
174 votes
rafacampoamor
supported this idea
·
-
14 votes
rafacampoamor
supported this idea
·
-
12 votes
rafacampoamor
supported this idea
·
-
43 votes
rafacampoamor
supported this idea
·
-
73 votes
rafacampoamor
supported this idea
·
-
89 votes
rafacampoamor
supported this idea
·
-
86 votes
rafacampoamor
supported this idea
·
-
905 votes
rafacampoamor
supported this idea
·
-
107 votes
rafacampoamor
supported this idea
·
-
1,312 votes
rafacampoamor
supported this idea
·
-
759 votes
rafacampoamor
supported this idea
·
-
579 votes
rafacampoamor
supported this idea
·
-
462 votes
rafacampoamor
supported this idea
·
-
359 votes
rafacampoamor
supported this idea
·
-
509 votes
rafacampoamor
supported this idea
·
While browser extension support is great, Proton Pass for macOS still lacks the native 'Credential Provider' extension.
On macOS Tahoe, even if we disable Apple Passwords, the system does not recognize Proton Pass as an available provider under System Settings > Passwords > Password Options. This creates a major friction point:
Passkey Hijacking: macOS keeps prompting to use iCloud Keychain or an external device because it doesn't 'see' Proton Pass as a system-wide vault.
Native App Autofill: We cannot use Proton Pass to autofill credentials in native apps (Slack, Terminal, etc.), only in browsers.
Firefox/Safari Issues: Users are forced to use advanced workarounds (like about:config in Firefox) to prevent macOS from overriding the Proton extension.
We need the macOS app to have the same system-level integration that the iOS app already has. This is the missing link for a truly 'Apple-free' security workflow.