$ pijul id ed
Editing identity: default
✔ Unique identity name · default
✔ Display name · Mike
✔ Email (leave blank for none) · mpech@tuta.io
✔ Do you want to change the encryption? (Current status: not encrypted) · no
✔ Do you want this key to expire? (Current expiry: never) · no
✔ Do you want to link this identity to a remote? · yes
✔ Remote username · tankf33der
✔ Remote URL · ssh.pijul.com
✔ Do you want to change the default SSH key? (Current key: none) · no
Linking identity tankf33der@ssh.pijul.com
Warning: Unable to automatically authenticate with server. Please make sure your SSH keys have been uploaded to the Nest.
For more information, please visit https://pijul.org/manual/the_nest/public_keys.html#ssh-public-keys
✔ Password for mpech@ssh.pijul.com · ********
Error: Could not prove identity default. Please check your credentials & network connection. If you are on an enterprise network, perhaps try running with `--no-cert-check`
$

Now i can not commit to nest with keys it always asking password and records comes from unknown user.

These patches should help in only proving identities when required. Does that fix your issue?

Never worked with patches from issue, how to pull?

I can reproduce this issue. @finchie: tankf33der has a different Nest handle and Linux login, and so do I.

In our cases, the suggested hostname is “ssh.pijul.com”, which we accept as it is. But then Pijul interprets “ssh.pijul.com” as a “remote”, i.e. either an SSH host or a URL, or maybe a path. In the case of SSH, that remote doesn’t have a username.

I’m working on a fix.