rafacampoamor
My feedback
42 results found
-
312 votesrafacampoamor
supported this idea
·
-
398 votesrafacampoamor
supported this idea
·
-
855 votesrafacampoamor
supported this idea
·
-
71 votesrafacampoamor
supported this idea
·
-
154 votes
An error occurred while saving the comment rafacampoamor
supported this idea
·
-
56 votesrafacampoamor
supported this idea
·
-
168 votesrafacampoamor
supported this idea
·
-
14 votesrafacampoamor
supported this idea
·
-
12 votesrafacampoamor
supported this idea
·
-
42 votesrafacampoamor
supported this idea
·
-
71 votesrafacampoamor
supported this idea
·
-
87 votesrafacampoamor
supported this idea
·
-
84 votesrafacampoamor
supported this idea
·
-
893 votesrafacampoamor
supported this idea
·
-
105 votesrafacampoamor
supported this idea
·
-
1,296 votesrafacampoamor
supported this idea
·
-
612 votesrafacampoamor
supported this idea
·
-
554 votesrafacampoamor
supported this idea
·
-
448 votesrafacampoamor
supported this idea
·
-
345 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.