flathub / flathub/com.github.IsmaelMartinez.teams_for_linux
Passkey FIDO2 Support
- Dominant language
- No language data
- Stars
- 3
- Forks
- 13
- Avg merge
- 2h 23m
- Merged PRs (30d)
- 10
Description
When using this flatpak, the login will never show and only hang a the login mask with the loading bar at the top. This happens when a Second factor is used that is not old 2FA based (so FIDO2 or Passkey). Normally the attempt will fail and you can go back to select another method. That worked well until the latest release. I think that with one of the latest releases they added proper support for FIDO2 as hinted by this PR: https://github.com/IsmaelMartinez/teams-for-linux/issues/2887
I guess this library is needed for the prompt to show/work. Unfortunately I do not know what's necessary to add that. As shown by ldd, there are a couple of libs that would need to also be included. But I guess you guys know that better then I do.
```bash
$ ldd *
fido2-assert:
linux-vdso.so.1 (0x00007fbf562b2000)
libcrypto.so.3 => /lib64/libcrypto.so.3 (0x00007fbf55c00000)
libfido2.so.1 => /lib64/libfido2.so.1 (0x00007fbf5624d000)
libc.so.6 => /lib64/libc.so.6 (0x00007fbf55a07000)
libz.so.1 => /lib64/libz.so.1 (0x00007fbf56223000)
libcbor.so.0.13 => /lib64/libcbor.so.0.13 (0x00007fbf56211000)
libudev.so.1 => /lib64/libudev.so.1 (0x00007fbf561c5000)
/lib64/ld-linux-x86-64.so.2 (0x00007fbf562b4000)
libgcc_s.so.1 => /lib64/libgcc_s.so.1 (0x00007fbf56196000)
fido2-cred:
linux-vdso.so.1 (0x00007fca4e71c000)
libcrypto.so.3 => /lib64/libcrypto.so.3 (0x00007fca4e000000)
libfido2.so.1 => /lib64/libfido2.so.1 (0x00007fca4e6b5000)
libc.so.6 => /lib64/libc.so.6 (0x00007fca4de07000)
libz.so.1 => /lib64/libz.so.1 (0x00007fca4e68b000)
libcbor.so.0.13 => /lib64/libcbor.so.0.13 (0x00007fca4e679000)
libudev.so.1 => /lib64/libudev.so.1 (0x00007fca4e62d000)
/lib64/ld-linux-x86-64.so.2 (0x00007fca4e71e000)
libgcc_s.so.1 => /lib64/libgcc_s.so.1 (0x00007fca4e5fe000)
fido2-token:
linux-vdso.so.1 (0x00007f8ff9dcf000)
libcrypto.so.3 => /lib64/libcrypto.so.3 (0x00007f8ff9800000)
libfido2.so.1 => /lib64/libfido2.so.1 (0x00007f8ff97c7000)
libcbor.so.0.10 => not found
libz.so.1 => /lib64/libz.so.1 (0x00007f8ff9d70000)
libc.so.6 => /lib64/libc.so.6 (0x00007f8ff95ce000)
libcbor.so.0.13 => /lib64/libcbor.so.0.13 (0x00007f8ff95bc000)
libudev.so.1 => /lib64/libudev.so.1 (0x00007f8ff9570000)
/lib64/ld-linux-x86-64.so.2 (0x00007f8ff9dd1000)
libgcc_s.so.1 => /lib64/libgcc_s.so.1 (0x00007f8ff9543000)
```
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reproducing the login hang in the Flatpak with a FIDO2 or passkey second factor, then inspect how the packaged application includes the fido2-assert, fido2-cred, and fido2-token dependencies listed in the report. Compare the required libfido2, libcbor, libudev, libcrypto, and z libraries, and verify that the FIDO2 prompt appears and login can complete or return to method selection.
Written by the indexing model from the issue text.
Assessment
- Domain
- authentication, desktop, security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100