On Sun, 11 Sep 2016 at 16:37:33 +0200, Marcus Frings wrote: > On Sun, 11 Sep 2016 15:46:58 +0200, Guilhem Moulin <guil...@guilhem.org> > wrote: > >> Still, I can't reproduce this. Could you try to pass ‘--debug-level >> basic’ to the recv-key command? > > I patched caff with the diff file you suggested, but the output is > still the same, hence not even additional debugging information (see > attached txt file).
My bad, this debug level isn't very useful indeed. Could you try to
replace ‘--debug-level basic’ by ‘--debug ipc’? The output is quite
verbose as it includes the downloaded armored key, but I'd like to see
how gpg interacts with dirmngr. For instance,
~$ gpg --keyserver hkps://hkps.pool.sks-keyservers.net --debug ipc
--recv-keys 39278DA8109E6244
gpg: reading options from '/home/guilhem/.gnupg/gpg.conf'
gpg: enabled debug flags: ipc
gpg: DBG: chan_3 <- # Home: /home/guilhem/.gnupg
gpg: DBG: chan_3 <- # Config: /home/guilhem/.gnupg/dirmngr.conf
gpg: DBG: chan_3 <- OK Dirmngr 2.1.15 at your service
gpg: DBG: connection to the dirmngr established
gpg: DBG: chan_3 -> GETINFO version
gpg: DBG: chan_3 <- D 2.1.15
gpg: DBG: chan_3 <- OK
gpg: DBG: chan_3 -> KEYSERVER --clear hkps://hkps.pool.sks-keyservers.net
gpg: DBG: chan_3 <- OK
gpg: DBG: chan_3 -> KS_GET -- 0x39278DA8109E6244
gpg: DBG: chan_3 <- S PROGRESS tick ? 0 0
gpg: DBG: chan_3 <- S SOURCE https://sks.spodhuis.org:443
gpg: DBG: chan_3 <- D -----BEGIN PGP PUBLIC KEY BLOCK-----%0A
[…]
gpg: DBG: chan_3 <- D -----END PGP PUBLIC KEY BLOCK-----%0D%0A
gpg: DBG: chan_3 <- OK
gpg: key 39278DA8109E6244: "Guilhem Moulin" not changed
gpg: Total number processed: 1
gpg: unchanged: 1
gpg: DBG: chan_3 -> BYE
gpg: secmem usage: 0/65536 bytes in 0 blocks
>> If this doesn't produce anything useful, could you also enable debug
>> output for dirmngr? For instance by adding
>>
>> debug-level basic
>> log-file /run/user/1000/dirmngr.log
>>
>> to ~/.gnupg/dirmngr.conf.
>
> I also added these two lines, but when I run caff (or gpg manually)
> this logfile is not created at all.
You'll need to restart dirmngr for the options to take effect. Here is
the debug output produced by the gpg command above:
dirmngr[25056.0] handler for fd 0 started
dirmngr[25056.0] DBG: chan_0 -> # Home: /home/guilhem/.gnupg
dirmngr[25056.0] DBG: chan_0 -> # Config: /home/guilhem/.gnupg/dirmngr.conf
dirmngr[25056.0] DBG: chan_0 -> OK Dirmngr 2.1.15 at your service
dirmngr[25056.0] connection from process 25409 (1000:1000)
dirmngr[25056.0] DBG: chan_0 <- GETINFO version
dirmngr[25056.0] DBG: chan_0 -> D 2.1.15
dirmngr[25056.0] DBG: chan_0 -> OK
dirmngr[25056.0] DBG: chan_0 <- KEYSERVER --clear
hkps://hkps.pool.sks-keyservers.net
dirmngr[25056.0] DBG: chan_0 -> OK
dirmngr[25056.0] DBG: chan_0 <- KS_GET -- 0x39278DA8109E6244
dirmngr[25056.0] DBG: chan_0 -> S PROGRESS tick ? 0 0
dirmngr[25056.0] DBG: chan_0 -> S SOURCE https://sks.spodhuis.org:443
dirmngr[25056.0] DBG: chan_0 -> D -----BEGIN PGP PUBLIC KEY BLOCK-----%0A
[…]
dirmngr[25056.0] DBG: chan_0 -> D -----END PGP PUBLIC KEY BLOCK-----%0D%0A
dirmngr[25056.0] DBG: chan_0 -> OK
dirmngr[25056.0] DBG: chan_0 <- BYE
dirmngr[25056.0] DBG: chan_0 -> OK closing connection
dirmngr[25056.0] handler for fd 0 terminated
Cheers,
--
Guilhem.
signature.asc
Description: PGP signature
