From: Achim Gratz <Stromeko@nexgo.de>
To: cygwin-apps@cygwin.com
Subject: FIDO/U2F middleware libraries
Date: Sun, 14 Nov 2021 16:53:14 +0100 [thread overview]
Message-ID: <87k0ha91jp.fsf@Rainer.invalid> (raw)
So I've got myself some FIDO2 tokens to eventually use with OpenSSH and
that works. However, you need to be administrator to access the HID
interface on Win10 past 1909 or so or else go through their
"WindowsHello" API. I've found two middleware libraries that almost
build out of the box on Cygwin:
https://github.com/tavrez/openssh-sk-winhello
https://github.com/mgbowen/windows-fido-bridge
They both work on 64bit only (the first one builds on 32bit, but
crashes, the second one doesn'tr even build). If anybody wants to have
a look, here are the package sources on playground:
https://cygwin.com/git-cygwin-packages?p=git/cygwin-packages/playground.git;a=shortlog;h=refs/heads/libwinhello
https://cygwin.com/git-cygwin-packages?p=git/cygwin-packages/playground.git;a=shortlog;h=refs/heads/libwindowsfidobridge
The build artefacts are on AppVeyor.
There is a newer version of libfido (which OpenSSH uses) that should be
able to use the WindowsHello. Corinna has patched it up to the point
were it actually builds and OpenSSH tries to use it, but fails. I have
no idea yet if the fail is triggered by something OpenSSH does or
seomthing in libfido not lining up with WindowsHello. I have to get up
to speed on how to use the fido-tools provided with libfido in order to
see where things go sideways.
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
SD adaptation for Waldorf Blofeld V1.15B11:
http://Synth.Stromeko.net/Downloads.html#WaldorfSDada
next reply other threads:[~2021-11-14 15:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-14 15:53 Achim Gratz [this message]
2021-11-14 17:05 ` Achim Gratz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87k0ha91jp.fsf@Rainer.invalid \
--to=stromeko@nexgo.de \
--cc=cygwin-apps@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).