Touch ID/Biometric authentication not available

[rvsit]

In the current build of ungoogled chromium on macos there is no option to authenticate with Touch ID through webauthn.

Steps to reproduce:

• Go to webauthn.io.
• Fill in a username and click register.
• Chrome will show "This device" as an option, which triggers TouchID, Ungoogle Chromium does not.

Left is Ungoogled Chromium, right is Chrome

I understand this might have something to do with signatures, is there anything we could do to possibly self sign it or something?

[networkException]

Does this work in vanilla chromium?

[rvsit]

Unsure, but it seems to have something to do with the signature/entitlements, see https://chromium.googlesource.com/chromium/src/+/lkgr/device/fido/mac/touch_id_context.mm
So I don't think there is anything we can do to fix it?

[PF4Public]

This is an old issue, that didn't show much activity recently and probably lost its significance — closing.
If you have any more information to add, let us know.

[MrChocolatine]

Can we reopen this ticket please? This is still an issue, for instance with GitHub:

• Version used: 122.0.6261.69

[PF4Public]

Sure, to improve the visibility, but apart from that it could very well be that this issue is inherently unsolvable.

[MrChocolatine]

Sure, to improve the visibility, but apart from that it could very well be that this issue is inherently unsolvable.

because of this previous message? #93 (comment)

[PF4Public]

because of this previous message? #93 (comment)

Partially, yes. Someone has to debug it, but no one seems to be eager enough.

[MrChocolatine]

Unfortunately I do not have the knowledge to help, not my field.

[Cubik65536]

@MrChocolatine Can you confirm how this behaves on Vanilla Chromium (Chromium w/ Google)?

[MrChocolatine]

@Cubik65536

I cannot test with vanilla Chromium as it conflicts with Ungoogled-Chromium:

➜  ~ brew install --cask chromium
==> Downloading https://formulae.brew.sh/api/cask.jws.json
...
Error: Cask 'chromium' conflicts with 'eloston-chromium'.

Maybe there is a way to bypass this conflict I am not aware of.

[Cubik65536]

@Cubik65536

I cannot test with vanilla Chromium as it conflicts with Ungoogled-Chromium:

➜  ~ brew install --cask chromium
==> Downloading https://formulae.brew.sh/api/cask.jws.json
...
Error: Cask 'chromium' conflicts with 'eloston-chromium'.

Maybe there is a way to bypass this conflict I am not aware of.

Don't download via HomeBrew, just download dmg from Chromium site and directly run the .app.

[Cubik65536]

Any updates? And can you check if signed binaries at https://github.com/claudiodekker/ungoogled-chromium-binaries works with this? /cc @MrChocolatine

[MrChocolatine]

Don't download via HomeBrew, just download dmg from Chromium site and directly run the .app.

Still unable to execute Chromium:

“Chromium.app” is damaged and can’t be opened. You should move it to the Bin.

And I tried several times.

[Cubik65536]

Don't download via HomeBrew, just download dmg from Chromium site and directly run the .app.

Still unable to execute Chromium:

“Chromium.app” is damaged and can’t be opened. You should move it to the Bin.

And I tried several times.

@MrChocolatine Right-Click the app, select open, and then the system will prompt you with the option to run anyway.

[Cubik65536]

Oh I might misunderstood your issue, you need to download the version with the right architecture (arm or intel). The Chromium page seems to provide only one.

[MrChocolatine]

Yep, that's what I did and I get the above error.
I just tried again and same result when running the .app file, even with Ungoogled-Chromium closed.

https://download-chromium.appspot.com/dl/Mac_arm?type=snapshots

[Cubik65536]

Ummm, this runs very well for me. Are you running M-series chips?

[Cubik65536]

I tested on Vanilla Chromium, and it seems that auth doesn't work either with Vanilla Chromium...

I got a different prompt though (it is just the QR Code with a message saying USB key is available as option). Do you have the most recent version of UGC? If not, can you update and test again? /cc @MrChocolatine

[RobusK]

This was also discussed here: ungoogled-software/ungoogled-chromium#2606

Apparently it's because of a missing entitlement: https://developer.apple.com/documentation/bundleresources/entitlements/com_apple_developer_web-browser_public-key-credential?changes=_3