Hello,
I have trouble understanding the socket aspect of the ssh support in
GnuPG. I use the following setup (only including the relevant lines):
---
*FILE: ~/.profile
export GNUPGHOME="$XDG_DATA_HOME"/gnupg
GPG_TTY="$(tty)"; export GPG_TTY
# unset SSH_AGENT_PID
# export SSH_AUTH_SOCK="$GNUPGHOM
Hi, Damien.
Jun 22, 2022, 20:19 by dgouttegat...@incenp.org:
> Yes. `gnupg_SSH_AUTH_SOCK_by` is set by the agent at the same time as
> `SSH_AUTH_SOCK` (...)
> The `gpgconf` thing is to make sure `SSH_AUTH_SOCK` is always set to
> the correct path (...).
Thank you for the explanation...
> In mos
Hi there!
I am encountering a certain warning regarding my ed25519/cv25519
encryption key. When I export the freshly generated encryption subkey
and then reimport it, I get the following:
>gpg: Schlüssel 20628B8C51751C49: "some name "
>nicht geändert
>gpg: warning: lower 3 bits of the secret key
Hi, Ingo.
Aug 22, 2022, 21:07 by kloec...@kde.org:
>> gpg2 --version
>> >
>> >gpg (GnuPG) 2.3.3
>> >libgcrypt 1.9.4
>>
>
> The solution is easy: Use gpg 2.3.7.
>
Are you sure this should suffice? I went back and rebuilt my libgcrypt and
GnuPG to the latest stable versions and I still get this
Thank you for taking the time to test, Ingo.
Aug 23, 2022, 10:18 by kloec...@kde.org:
> Yes, I'm pretty sure. I followed your steps in a fresh GNUPGHOME and didn't
> see the warning message. I didn't protect the test keys with a passphrase
> though.
>
The use of passphrase may be responsible.
