Beta for 2.1.1 available
Hugo Hinterberger
hugo.hinterberger at gmx.net
Tue Nov 25 12:41:27 CET 2014
On Tue, 25 Nov 2014 10:57:34 +0100, Kristian Fiskerstrand
<kristian.fiskerstrand at sumptuouscapital.com> wrote:
> On 11/25/2014 10:50 AM, Hugo Hinterberger wrote:
>> Hi Kristian,
>>
>> On Mon, 24 Nov 2014 21:40:22 +0100, Kristian Fiskerstrand
>> <kristian.fiskerstrand at sumptuouscapital.com> wrote:
>>
>>> For 2.1 you need the following in dirmngr.conf: hkp-cacert
>>> /path/to/sks-keyservers.netCA.pem
>>>
>
> ...
>
>>
>> Both fail. Using hkp, on the other hand, works.
>>
>
>
> Try using --debug 1024 and see what the dirmngr output is. One
> possibility is that it is related to [0]
I ran:
dirmngr.exe --debug 1024 --daemon --homedir
C:/Users/<username>/AppData/Roaming/gnupg
and
gpg --debug 1024 --keyserver=hkps://hpks.pool.sks-keyservers.net
--recv-key 0x8BCF070743176C6A
and get the following output:
dirmngr:
dirmngr[7012]: reading options from
'C:/Users/<username>/AppData/Roaming/gnupg/dirmngr.conf'
dirmngr[7012]: NOTE: this is a development version!
dirmngr.log:
2014-11-25 11:46:24 dirmngr[7012] listening on socket
'C:\Users\<username>\AppData\Roaming\gnupg\S.dirmngr'
2014-11-25 11:46:24 dirmngr[7012] permanently loaded certificates: 0
2014-11-25 11:46:24 dirmngr[7012] runtime cached certificates: 0
2014-11-25 11:46:33 dirmngr[7012] handler for fd 232 started
2014-11-25 11:46:33 dirmngr[7012] DBG: chan_000000E8 -> # Home:
C:/Users/<username>/AppData/Roaming/gnupg
2014-11-25 11:46:33 dirmngr[7012] DBG: chan_000000E8 -> # Config:
C:/Users/<username>/AppData/Roaming/gnupg/dirmngr.conf
2014-11-25 11:46:33 dirmngr[7012] DBG: chan_000000E8 -> OK Dirmngr
2.1.1-beta35 at your service
2014-11-25 11:46:33 dirmngr[7012] handler for fd 244 started
2014-11-25 11:46:33 dirmngr[7012] DBG: chan_000000F4 -> # Home:
C:/Users/<username>/AppData/Roaming/gnupg
2014-11-25 11:46:33 dirmngr[7012] DBG: chan_000000F4 -> # Config:
C:/Users/<username>/AppData/Roaming/gnupg/dirmngr.conf
2014-11-25 11:46:33 dirmngr[7012] DBG: chan_000000F4 -> OK Dirmngr
2.1.1-beta35 at your service
2014-11-25 11:46:33 dirmngr[7012] DBG: chan_000000F4 <- KEYSERVER --clear
hkps://hpks.pool.sks-keyservers.net
2014-11-25 11:46:33 dirmngr[7012] DBG: chan_000000F4 -> OK
2014-11-25 11:46:33 dirmngr[7012] DBG: chan_000000F4 <- KEYSERVER
hkps://hkps.pool.sks-keyservers.net
2014-11-25 11:46:33 dirmngr[7012] DBG: chan_000000F4 -> OK
2014-11-25 11:46:33 dirmngr[7012] DBG: chan_000000F4 <- KS_GET --
0x8BCF070743176C6A
2014-11-25 11:46:33 dirmngr[7012] command 'KS_GET' failed: No keyserver
available
2014-11-25 11:46:33 dirmngr[7012] DBG: chan_000000F4 -> ERR 167772346 No
keyserver available <Dirmngr>
2014-11-25 11:46:33 dirmngr[7012] DBG: chan_000000F4 <- BYE
2014-11-25 11:46:33 dirmngr[7012] DBG: chan_000000F4 -> OK closing
connection
2014-11-25 11:46:33 dirmngr[7012] handler for fd 244 terminated
2014-11-25 11:46:33 dirmngr[7012] DBG: chan_000000E8 <- [eof]
2014-11-25 11:46:33 dirmngr[7012] handler for fd 232 terminated
gpg:
gpg: reading options from
'C:/Users/<username>/AppData/Roaming/gnupg/gpg.conf'
gpg: NOTE: THIS IS A DEVELOPMENT VERSION!
gpg: It is only intended for test purposes and should NOT be
gpg: used in a production environment or with production keys!
gpg: enabled debug flags: extprog assuan
gpg: DBG: chan_000000D4 <- # Home:
C:/Users/<username>/AppData/Roaming/gnupg
gpg: DBG: chan_000000D4 <- # Config:
C:/Users/<username>/AppData/Roaming/gnupg/dirmngr.conf
gpg: DBG: chan_000000D4 <- OK Dirmngr 2.1.1-beta35 at your service
gpg: DBG: chan_000000D8 <- # Home:
C:/Users/<username>/AppData/Roaming/gnupg
gpg: DBG: chan_000000D8 <- # Config:
C:/Users/<username>/AppData/Roaming/gnupg/dirmngr.conf
gpg: DBG: chan_000000D8 <- OK Dirmngr 2.1.1-beta35 at your service
gpg: DBG: connection to the dirmngr established
gpg: DBG: chan_000000D8 -> KEYSERVER --clear
hkps://hpks.pool.sks-keyservers.net
gpg: DBG: chan_000000D8 <- OK
gpg: DBG: chan_000000D8 -> KEYSERVER hkps://hkps.pool.sks-keyservers.net
gpg: DBG: chan_000000D8 <- OK
gpg: DBG: chan_000000D8 -> KS_GET -- 0x8BCF070743176C6A
gpg: DBG: chan_000000D8 <- ERR 167772346 No keyserver available <Dirmngr>
gpg: keyserver receive failed: No keyserver available
gpg: DBG: chan_000000D8 -> BYE
gpg: secmem usage: 0/32768 bytes in 0 blocks
> References:
> [0]
> http://lists.gnupg.org/pipermail/gnupg-users/2014-November/051471.html
Seems to me to be a slightly different issue.
As a side-note: Inoticed error messages for missing directories and files:
%appdata%/gnupg/trusted-certs/
%appdata%/gnupg/extra-certs/
%appdata%/gnupg/dirmngr_ldapservers.conf
%appdata%/gnupg/ldapservers.conf
I created those files and folders and placed a hardlink to the
.pem-certificate in the trusted-certs folder.
Regrads,
Hugo
More information about the Gnupg-users
mailing list