Bitwarden is a password manager, like KeePassXC and has a self-hosted 
variant Vaultwarden. Starting around November 2023, Bitwarden failed to 
login on Chromium on OpenBSD, both the extension and the website now 
fail to log me in with this error:

Webassembly support is required for the Argon2 KDF feature.

This same error is documented with screenshot in Edge for Windows on 
Bitwarden's community forums. Re-installing Edge fixed the problem.

https://community.bitwarden.com/t/bitwarden-an-error-has-occurred-webassembly-support-is-required-for-the-argon2-kdf-feature/57466 


Bitwarden works fine in Firefox on OpenBSD and fine in Firefox and 
Chromium on FreeBSD and Fedora. I think it's possible Chromium on 
OpenBSD was built with webassembly in a deprecated state starting 
November 2023, requiring the --with-wasm flag per the manpage, and then 
that flag stopped working and disappeared from the manpage altogether in 
about September 2024.

Bitwarden specifically uses the argon2id variant of Argon2.

https://github.com/P-H-C/phc-winner-argon2

https://bitwarden.com/search/?q=argon2

On request, I can provide dmesg's for 7.5, 7.6-release, current from 
around August 2024 where the --with-wasm still worked, and a snapshot 
from later in September 2024 where the feature and flag are just gine.

It's possible for me to switch my entire Bitwarden account to the older 
PBKDF2 with SHA-256, just for Chromium on OpenBSD. But I would prefer to 
stick with the latest recommended key derivation function. If excluding 
webassembly was intentional on the part of the port maintainer, perhaps 
could there be a webassembly flavor for those of us who really benefit 
from this feature?