Seems as per this comment on the github PR this will not be merged.
Instead bitwarden wants to use a native implementation (on windows and macos) with linux support even further out.
They can do it either way they want, but it’s 2024 and Bitwarden still doesn’t support FIDO2 keys throughout all platforms. This is a disappointment.
1 Like
I wonder what Keeper is doing differently on their end. My Fido2 Yubikey works with their Linux desktop app. The only thing that I have noticed that doesn’t seem to be working in the Linux app is using a PIN with the Yubikey.
Most likely they are just using libfido2. Bitwarden can do that too, (aside from on Flatpak), but it requires development effort, and most likely more UI support (for instance, for the PIN), as the platform does not give any UI support (as opposed to Mac/Windows).
Is there any offical update on this?
2 Likes
Do we have an update on this?
1 Like
NotACat
December 3, 2024, 4:18am
89
Any updates?
I am a premium user. It’s been years now. It’s pretty jarring to not be able to safeguard ALL my passwords with hardware keys in (almost) 2025.
1 Like
@NotACat I guess there is an update on this… see this (yesterday’s) discussion on Reddit here: https://www.reddit.com/r/Bitwarden/s/QwiPaUflzB
1 Like
It seems, FIDO2-2FA support for the MacOS desktop app will arrive with version 2025.2.1:
(–> Release Notes 2025.2.1 )
2 Likes
main
← km/fido-2-on-linux
opened 10:44PM - 23 Jan 25 UTC
## 🎟️ Tracking
https://bitwarden.atlassian.net/browse/PM-18884
https://for… um.snapcraft.io/t/autoconnect-u2f-devices-to-bitwarden-desktop/46028
## 📔 Objective
Electron on Linux just supports fido2, same thing as with mac applies, no pinentry.
Sandboxed linux (snap/flatpak) need some further permissions before they can be enabled.
- u2f-devices plug (for fido2 usb authenticators) on snap
- devices permission on flatpak
## 📸 Screenshots
[Screencast_20250304_153130.webm](https://github.com/user-attachments/assets/8612aca8-603e-445a-bd7b-e5a3153bc734)
## ⏰ Reminders before review
- Contributor guidelines followed
- All formatters and local linters executed and passed
- Written new unit and / or integration tests where applicable
- Protected functional changes with optionality (feature flags)
- Used internationalization (i18n) for all UI strings
- CI builds passed
- Communicated to DevOps any deployment requirements
- Updated any necessary documentation (Confluence, contributing docs) or informed the documentation team
## 🦮 Reviewer guidelines
- 👍 (`:+1:`) or similar for great changes
- 📝 (`:memo:`) or ℹ️ (`:information_source:`) for notes or general info
- ❓ (`:question:`) for questions
- 🤔 (`:thinking:`) or 💭 (`:thought_balloon:`) for more open inquiry that's not quite a confirmed issue and could potentially benefit from discussion
- 🎨 (`:art:`) for suggestions / improvements
- ❌ (`:x:`) or ⚠️ (`:warning:`) for more significant problems or concerns needing attention
- 🌱 (`:seedling:`) or ♻️ (`:recycle:`) for future improvements or indications of technical debt
- ⛏ (`:pick:`) for minor or nitpick changes
has also just merged and will also be available in an upcoming release!
1 Like