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 know that this is a contrived setup (hence it probably wasn't reported), just making sure this is tracked.
Steps to Reproduce the Problem
Have a yubikey or similar
Configure a gpg auth subkey to be used for SSH and export it to the hw key
Configure gpg to use pinentry-ncurses for card pin
Expected Behavior
When you do fetch/push, pinentry should ask for the pin and then everything should work.
Actual Behavior
Instead you get the classic Error: authentication required but no callback set; class=Ssh (23); code=Auth (-16).
If you ssh into something once for the pin to get cached it starts working (without asking for pin, obviously).
When it was not pinentry-curses but whatever was the default it worked fine, asking for the pin the one time with a separate dialog window.
And the most interesting thing is that gpg signing works! When you snapshot or whatever for the first time after boot it asks for the pin with pinentry and works just fine. Probably because for gpg we just call the gpg binary and for ssh it's another libssh issue - so this likely may be fixed by the openssh build.
Specifications
Platform: NixOS
Version: 0.20.0
The text was updated successfully, but these errors were encountered:
Description
I know that this is a contrived setup (hence it probably wasn't reported), just making sure this is tracked.
Steps to Reproduce the Problem
Expected Behavior
When you do fetch/push, pinentry should ask for the pin and then everything should work.
Actual Behavior
Instead you get the classic
Error: authentication required but no callback set; class=Ssh (23); code=Auth (-16)
.If you ssh into something once for the pin to get cached it starts working (without asking for pin, obviously).
When it was not pinentry-curses but whatever was the default it worked fine, asking for the pin the one time with a separate dialog window.
And the most interesting thing is that gpg signing works! When you snapshot or whatever for the first time after boot it asks for the pin with pinentry and works just fine. Probably because for gpg we just call the gpg binary and for ssh it's another libssh issue - so this likely may be fixed by the openssh build.
Specifications
The text was updated successfully, but these errors were encountered: