-
-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Does not work with systemd-homed
#18
Comments
Here is a Logcat dump, with the app set to "Debug" logging: https://gist.github.com/Thesola10/98146c3db20051ffacf07598ea84202f |
Documentation for |
Yep, that's the issue. Since |
Your comment in #5 mentions that |
It is implemented according to my understanding of the spec back at the time, but I remember the spec being unclear about some things (see WearAuthn/authenticator/src/main/java/me/henneke/wearauthn/fido/ctap2/Authenticator.kt Line 354 in 35b2e91
|
Given the |
Browsing through the logcat, weirdly enough, there's never an error or warning on the watch side of things, not even a claim of a "malformed message". Pausing the authentication process before the second step yields an interesting behavior: WearAuthn logs absolutely nothing. The issue might be on PS: The WearAuthn watch does not show up when I do |
Managed to get https://gist.github.com/Thesola10/4639fdb4d5d82e8d0fc1251aacb81219 |
any update? |
What went wrong?
systemd-homed
is a software solution for Linux user accounts that accepts FIDO2 tokens as an alternative for the user password, essentially providing a Chromebook- or macOS-esque "Log in with watch" feature if combined with WearAuthn.And that's where the issue occurs:
systemd-homed
fails to register my watch as a login token.Steps to reproduce
systemd-homed
homectl update --fido2-device=/dev/hidraw2
to register the watch as a login token (exacthidraw
path may vary)io.systemd.home
("Home Directory"), accept it.systemd-homed
then errors out with the following error:WebAuthn works perfectly through Firefox, through Flatpak, so it can't possibly be a permissions issue.
On a USB Yubikey, the correct behavior is that the key asks for presence twice. On WearAuthn, the second confirmation never happens.
Which model is your watch?
Fossil Q Explorist Gen 4
Which Android version is running on your watch?
Wear OS 2.34
Which version of WearAuthn are you using?
0.9.17 (Google Play)
I don't know how useful it is, but the app version also mentions "Credentials storage: Hardware".
The text was updated successfully, but these errors were encountered: