rafacampoamor
My feedback
42 results found
-
233 votesrafacampoamor
supported this idea
·
-
264 votesrafacampoamor
supported this idea
·
-
615 votesrafacampoamor
supported this idea
·
-
68 votesrafacampoamor
supported this idea
·
-
116 votes
An error occurred while saving the comment rafacampoamor
supported this idea
·
-
39 votesrafacampoamor
supported this idea
·
-
150 votesrafacampoamor
supported this idea
·
-
10 votesrafacampoamor
supported this idea
·
-
12 votesrafacampoamor
supported this idea
·
-
38 votesrafacampoamor
supported this idea
·
-
70 votesrafacampoamor
supported this idea
·
-
74 votesrafacampoamor
supported this idea
·
-
68 votesrafacampoamor
supported this idea
·
-
844 votesrafacampoamor
supported this idea
·
-
92 votesrafacampoamor
supported this idea
·
-
1,229 votesrafacampoamor
supported this idea
·
-
468 votesrafacampoamor
supported this idea
·
-
463 votesrafacampoamor
supported this idea
·
-
376 votesrafacampoamor
supported this idea
·
-
273 votesrafacampoamor
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.