You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I was looking into giving it a go to implement hybrid transports in particular QR-initiated Transactions on Linux to be able to also using a phone e.g. for SSH logins and maybe git signing.
The main communication flow would be to start the command and then
libfido2 displays a QR code (e.g. using libqrencode)
# Prepare an initial key pair for connecting to the tunnel service which is also included in the QR code
fido2-token -R hybrid:/path/to/a/state-file
# and the just normal usage.
fido2-cred -M -i cred_param hybrid:/path/to/a/state-file
# ...
Some of the open questions are:
While on the command line, we could just print the QR code to stdout. However, when this is integrated into another app, that's probably not the cleanest way.
How would enumeration work? (token_list --> fido_dev_info_manifest)
How would the state file look?
Would there be interest for this type of thing here?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
I was looking into giving it a go to implement hybrid transports in particular QR-initiated Transactions on Linux to be able to also using a phone e.g. for SSH logins and maybe git signing.
The main communication flow would be to start the command and then
Does this sound reasonable?
To enable State Assisted Transactions, some of the state could be saved to a file.
I imagine basic usage to work kind of like
Some of the open questions are:
stdout
. However, when this is integrated into another app, that's probably not the cleanest way.token_list
-->fido_dev_info_manifest
)Would there be interest for this type of thing here?
Beta Was this translation helpful? Give feedback.
All reactions