Hi! Thanks a lot for Fork!
I would like to request better support for SSH key in a yubikey. I recently moved my SSH key from my machine disk to my yubikey. This is an enhanced security model, were my private key cannot be exfiltrated. As an important note, the SSH key does NOT have a passphrase, all it requires for unlocking is a tap on the yubikey. It does, however, cause some quirks with Fork.
Now, whenever I do an operation that requires the SSH key, I need to physically tap my key. On console it looks like this:
For committing (with signed commits) I need to tap the yubikey twice (once for signing, another for pushing). However, in fork, this causes a window pop-up to appear asking for SSH passphrase. When I tap the key, the operation continues in the background (e.g. pull/push) but the password dialog is not dismissed:
Do you think it is possible to improve this and not show the dialog or at least dismiss the dialog once the background operation has been completed?
Hi! Thanks a lot for Fork!
I would like to request better support for SSH key in a yubikey. I recently moved my SSH key from my machine disk to my yubikey. This is an enhanced security model, were my private key cannot be exfiltrated. As an important note, the SSH key does NOT have a passphrase, all it requires for unlocking is a tap on the yubikey. It does, however, cause some quirks with Fork.
Now, whenever I do an operation that requires the SSH key, I need to physically tap my key. On console it looks like this:
For committing (with signed commits) I need to tap the yubikey twice (once for signing, another for pushing). However, in fork, this causes a window pop-up to appear asking for SSH passphrase. When I tap the key, the operation continues in the background (e.g. pull/push) but the password dialog is not dismissed:
Do you think it is possible to improve this and not show the dialog or at least dismiss the dialog once the background operation has been completed?