The sound distributed version control system

#732 [ID] failed link identity to a remote

Opened by tankf33der on November 19, 2022
tankf33der on November 19, 2022
$ 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`
$
tankf33der on November 19, 2022

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

finchie added a change on November 26, 2022
YJXRCXOSO2J5BFFR6QKFDVV3RJ5J3QXB4UZ3DVQZLYTF5RJ4TNJAC
finchie added a change on November 26, 2022
44RUBHREQUNI4B36WSV7CUK5CVVIKG2AQOQJQZ7HU3BHY6W6AUEQC
finchie on November 26, 2022

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

tankf33der on November 27, 2022

Never worked with patches from issue, how to pull?