I do backups and want to encrypt some of them. I also want to set this as a
cron job. The problem is, if I haven't used my signing key before the cron
daemon will attempt to encrypt backup files, gpg will throw that damn
pinentry window to ask for the passphrase I have already entered at the
startu
to be done
with the wrong key, and hence, the wrong username.
2014-02-14 10:23 GMT+04:00 Faru Guredo :
> Hello.
>
> I am migrating from ssh-agent to gpg-agent and have successfully loaded my
> SSH keys into the new agent,
>
> $ ssh-add -l
> 4096 5c:f3:b8:34:56:31:08:88:7b:4d
It worked with ssh-agent and still works without any agent -- settings in
~/.ssh/config just work as they should. But with gpg-agent there is such a
mess.
2014-02-15 18:19 GMT+04:00 Faru Guredo :
> After I have done small investigation, I've found that it's only the
> second tr
Hello.
I am migrating from ssh-agent to gpg-agent and have successfully loaded my
SSH keys into the new agent,
$ ssh-add -l
4096 5c:f3:b8:34:56:31:08:88:7b:4d:a3:ce:d8:9b:62:d7
/home/faru/.ssh/first-company (RSA)
4096 d9:14:07:00:15:c4:7b:70:c4:94:73:6c:bb:5d:25:42
/home/faru/.ssh/second-company
I’ve read GNU Privacy Handbook, the FAQ and thought I understood the
purpose of all four keys initially generated with --gen-keys.
But then I found this https://wiki.debian.org/subkeys and lost it.
tl;dr: There is suggested backup of ~/.gnupg, creation of a new pair of
subkeys for signing, then al
