On Wed, 2023-07-12 at 13:55 +0300, Teemu Likonen wrote:
> Secret keys are missing from this keyring, tells the "#" mark. Text
> "sec#" means that the primary secret key is missing and "ssb#" tells
> the
> same about secret subkeys. Those should read as "sec" and "ssb",
> without
> the "#" mark, or
* 2023-07-11 22:28:36-0500, Caleb Herbert wrote:
> But lately, I haven't been able to use SSH.
> sec# rsa3072 2023-06-29 [SC]
> 631CC434A56B5CBDFF21234697643795FA3E4BCE
> uid [ultimate] Caleb Herbert
> ssb# rsa3072 2023-06-29 [E]
> ssb# rsa2048 2023-06-29 [A]
Secret keys are
On 12.07.23 05:28, Caleb Herbert wrote:
> [caleb@farnsworth ~]$ export SSH_AUTH_SOCK=$(gpgconf --list-dirs agent-
> ssh-socket)
> [caleb@farnsworth ~]$ gpgconf --launch gpg-agent
> [caleb@farnsworth ~]$ ssh-add -L
> The agent has no identities.
>
Hi Caleb,
But you have the correct keygrip in `~/
I've followed the guide at
https://opensource.com/article/19/4/gpg-subkeys-ssh before, with
success. But lately, I haven't been able to use SSH.
I'll try to provide enough info below.
OS: Fedora Silverblue 38
[caleb@farnsworth ~]$ gpg --list-secret-keys
/var/home/caleb/.gnupg/pubring.kbx
--
On 7/11/23 21:30, Jacob Bachmeyer wrote:
Dennis Clarke via Gnupg-users wrote:
Dear GnuPG type folks :
I don't know what this means. Can we just compile with a decent C
compiler such as the LLVM/Clang in FreeBSD ?
[...]
Libgcrypt v1.10.2 has been configured as follows:
[...]
