Another convenient way is to use “~/.config/ssh”. This allows different
configurations per host without changing your global environment.
Example:
Host gitlab.com
HostName gitlab.com
User git
IdentityAgent ${XDG_RUNTIME_DIR}/gnupg/S.gpg-agent.ssh
Regards
Stephan
signature.asc
On Wed, Nov 22, 2023 at 8:57 PM Werner Koch wrote:
> Here is the snippet from by ~/.bashrc
I have a similar config. Thank you for the detailed explanation!
Only the following line does not work right after autologin (default
with Ubuntu / WSL2), seems like something is not ready yet.
On Tue, Nov 21, 2023 at 12:38 AM Ingo Klöcker wrote:
> $ gpg --export-ssh-key 1B6ED589
Thanks, this worked! I then added the key on the remote system to:
~/.ssh/authorized_keys
However, I could not log in. SSH reports:
Permission denied (publickey).
I then tried exporting the key
On Wed, 22 Nov 2023 19:39, Felix E. Klee said:
> However, I could not log in. SSH reports:
>
> Permission denied (publickey).
You need to make sure that the gpg-agent is running and the
SSH_AUTH_SOCK envvar is set correctly. Here is the snippet from by
~/.bashrc
--8<---cut
On Tue, Nov 21, 2023 at 12:38 AM Ingo Klöcker wrote:
> $ gpg --export-ssh-key 1B6ED589
Thanks, this worked! I then added the key on the remote system to:
~/.ssh/authorized_keys
However, I could not log in. SSH reports:
Permission denied (publickey).
I then tried exporting the key
Am Dienstag 21 November 2023 15:28:46 schrieb Aleksander Machniak:
> >> - v2.3 outputs two NO_SECKEY lines referring both recipient's and
> >> sender's keys.
Potentially the sender has encrypted the message for themselves, this would
explain why there are two potential decryption keys that you
