iCloud Password Extension about ungoogled-chromium-macos HOT 13 CLOSED

This has to do with that a NativeMessagingHosts file isn't being created for Chromium, but does for those other browsers.

To fix this you can copy the com.apple.passwordmanager.json from Vivaldi/Brave's NativeMessagingHosts folder into Chromium's, or simply run the following command in Terminal:

echo '{
    "name": "com.apple.passwordmanager",
    "description": "PasswordManagerBrowserExtensionHelper",
    "path": "/System/Cryptexes/App/System/Library/CoreServices/PasswordManagerBrowserExtensionHelper.app/Contents/MacOS/PasswordManagerBrowserExtensionHelper",
    "type": "stdio",
    "allowed_origins": [
        "chrome-extension://pejdijmoenmkgeppbflobdenhhabjlaj/",
        "chrome-extension://mfbcdcnpokpoajjciilocoachedjkima/"
    ]
}' > ~/Library/Application\ Support/Chromium/NativeMessagingHosts/com.apple.passwordmanager.json

from ungoogled-chromium-macos.

Thanks that has indeed fixed the issue. Surely though there should not be a need to fix this?

This is an issue of vanilla Chromium (you may already discovered), as ungoogled-chromium wants to stay as close as possible to vanilla, we might not fix it here. I do recommend you to report this to Chromium dev directly though.

Wrong info due to lack of prior research, check #144 (comment) for more info.

from ungoogled-chromium-macos.

To clarify, running the script above did indeed fix the problem, although I still think a permanent fix needs to be incorporated into the program itself. The need for manual fixes like this having to be applied is why I stopped using it.

NativeMessagingHosts should be installed by the extension rather than the browser, there’s absolutely nothing we can do, neither actually Chromium devs, you should report this to Apple if what you want is a permanent fix, otherwise I could only suggest you to use the temporary fix or stop using browsers that Apple haven’t considered at the first place.

from ungoogled-chromium-macos.

Reference: keeweb/keeweb@e674607 (another password manager that uses NativeMessagingHosts)

from ungoogled-chromium-macos.

I don't have this issue with Brave or Vivaldi.....

from ungoogled-chromium-macos.

Thanks that has indeed fixed the issue. Surely though there should not be a need to fix this?

from ungoogled-chromium-macos.

Does the proposed solution adequately fix this issue, can we close it?

from ungoogled-chromium-macos.

I can't say as I stopped using the program.

from ungoogled-chromium-macos.

Well, let's consider it solved for now then.

from ungoogled-chromium-macos.

To clarify, running the script above did indeed fix the problem, although I still think a permanent fix needs to be incorporated into the program itself. The need for manual fixes like this having to be applied is why I stopped using it.

from ungoogled-chromium-macos.

Interesting, I can't see that Apple have considered Vivaldi or Brave and they both work.

from ungoogled-chromium-macos.

Interesting, I can't see that Apple have considered Vivaldi or Brave and they both work.

Let me correct myself: "absolutely nothing no proper way".

Brave points their location to Chrome (code). Which:

1. Chromium doesn't, obviously.
2. They actually shouldn't do that. (I shall remind you this involves permission settings, permission to access passwords, I don't think anyone wants to share these kinds of permissions across different applications, especially when you don't even realize it's shared)

I could assume that Vivaldi do the same.

And I will go strongly against adding this for UGC. For the reason described above.

But, everyone can have a different standard for "proper way", other browser's dev thinks it's okay to share these hosts, it's not how I think, especially considering the nature of UGC.

from ungoogled-chromium-macos.

Fair enough I understand your position.

from ungoogled-chromium-macos.