Skip to content
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

Add support to pass a window handle to windows hello #857

Open
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

Nehluxhes
Copy link

Add support to pass a specific window handle to winhello WebAuthNAuthenticatorGetAssertion and WebAuthNAuthenticatorMakeCredential

Makes for better parenting of different application windows instead of just relying on GetForegroundWindow/GetTopWindow (they are still used if not setting anything)

Note the handle is supposed to be a HWND (just a pointer) but I could not find a clean way to either define it (but then redefinition errors) or avoid the whole including windows.h/windef.h mess in fido.h, so void* it is

Romain Braussen added 2 commits March 3, 2025 17:22
… methods to pass a specific window handle to use for the winhello UI
@LDVG
Copy link
Contributor

LDVG commented Mar 7, 2025

Thanks for the PR! 🙂

I've got two questions:

  1. Would it make more sense to have this as an attribute on the device (fido_dev_t) itself rather than the credential and assertion separately?
  2. Did I understand it correctly from the previous discussion that this essentially has no effect on resolving your issue?

@Nehluxhes
Copy link
Author

  1. It could. Could I reuse the io_handle then ? I don't think you are using it for winhello and the HWND could be considered an input handle.
  2. For now, unfortunately, no. If (when 🤞) microsoft fix it, it will though.

@LDVG
Copy link
Contributor

LDVG commented Mar 10, 2025

It could. Could I reuse the io_handle then ? I don't think you are using it for winhello and the HWND could be considered an input handle.

Sounds like a reasonable take to me

For now, unfortunately, no. If (when 🤞) microsoft fix it, it will though.

Is Microsoft aware of this issue?

@Nehluxhes
Copy link
Author

Is Microsoft aware of this issue?

Yes. I sent a mail to the address from the winhello repo and got an answer it has been forwarded to more people.
So at the very least it has been read. Too bad there is no public bug tracker to follow though.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

2 participants