[WIN] PublicKeyCredential API as a device fingerprint source

[uazo]

Preliminary checklist

• I have read the README.
• I have searched the existing issues for my problem. This is a new ticket, NOT a duplicate or related to another open issue.
• I have updated Cromite to the latest version. The bug is reproducible on this latest version.
• This is a bug report about the Cromite browser; not the website nor F-Droid nor anything else.

Can the bug be reproduced with corresponding Chromium version?

Yes

Are you sure?

Yes

Cromite version

132.0.6834.83

Device architecture

windows

Platform version

Windows 10

Android Device model

n/a

Is the device rooted?

I prefer not to write it

Changed flags

not important

Is this bug happening ONLY in an incognito tab?

No

Is this bug caused by the adblocker?

No

Is this bug a crash?

no

Describe the bug

in Windows, PublicKeyCredential API as a fingerprint source, as expose

• presence (or lack thereof) of a Bluetooth device
• activation (or not) of Windows Hello

Steps to reproduce the bug

await PublicKeyCredential.isUserVerifyingPlatformAuthenticatorAvailable();

true: windows hello active
false: windows hello not active (or guest mode)

and

await PublicKeyCredential.getClientCapabilities() 

hybridTransport: true -> presence of bluetooth

when it will become active

Expected behavior

hide data to websites

Screenshots

No response