Re: [Announce] GnuPG 2.1.9 released

[K. Raven]

Hi,

> Noteworthy changes in version 2.1.9 
> ===

> * dirmngr: Add option --keyserver.  Deprecate that option for gpg. 
> Install a dirmngr.conf file from a skeleton for new installations.

man dirmngr

--keyserver name

The scheme is the type of keyserver: "hkp" for the HTTP (or compatible)
keyservers, "ldap" for  the  LDAP keyservers,  or  "mailto"  for the
Graff email keyserver.

"hkps" (as in dirmngr-conf.skel)?

After the keyserver name, optional keyserver configuration options may
be provided. These are the  same as the global --keyserver-options from
below (where? in man gpg2?), but apply only to this particular keyserver.

keyserver hkps://hkps.pool.sks-keyservers.net option1 option2 or
keyserver hkps://hkps.pool.sks-keyservers.net option1,option2

in dirmngr.conf:

2015-10-10 14:04:46 dirmngr[18334.1] command 'KS_SEARCH' failed:
Syntaxfehler im URI
2015-10-10 14:04:46 dirmngr[18334.1] DBG: chan_1 -> ERR 167772206
Syntaxfehler im URI 

What is the right syntax? No example found in dirmngr-conf.skel.

Only with "keyserver hkps://hkps.pool.sks-keyservers.net" and
"keyserver-options" in gpg.conf, it works.

-- 
Ciao
Kai

http://kairaven.de/

___
Gnupg-users mailing list
Gnupg-users@gnupg.org
http://lists.gnupg.org/mailman/listinfo/gnupg-users

Re: Beta for 2.1.1 available

[K. Raven]

Hi Kristian,

> I reproduced this on a VM running $ gpg --version
> gpg (GnuPG) 2.1.1-beta40
> libgcrypt 1.7.0-beta122

I have tried it with

gpg --version
gpg (GnuPG) 2.1.1-beta35
libgcrypt 1.6.2

and had no problems:

gpg: sende Schlüssel 0x5A1796454623BA84 auf den hkps-Server
hkps.pool.sks-keyservers.net

dirmngr[18085.0] DBG: chan_0 -> # Home: /home/user/.gnupg
dirmngr[18085.0] DBG: chan_0 -> # Config: /home/user/.gnupg/dirmngr.conf
dirmngr[18085.0] DBG: chan_0 -> OK Dirmngr 2.1.1-beta35 at your service
dirmngr[18085.0] connection from process 27379 (1000:1000)
dirmngr[18085.1] Handhabungsroutine für fd 1 gestartet
dirmngr[18085.1] DBG: chan_1 -> # Home: /home/user/.gnupg
dirmngr[18085.1] DBG: chan_1 -> # Config: /home/user/.gnupg/dirmngr.conf
dirmngr[18085.1] DBG: chan_1 -> OK Dirmngr 2.1.1-beta35 at your service
dirmngr[18085.1] connection from process 27379 (1000:1000)
dirmngr[18085.1] DBG: chan_1 <- KEYSERVER --clear
hkps://hkps.pool.sks-keyservers.net
dirmngr[18085.1] DBG: chan_1 -> OK
dirmngr[18085.1] DBG: chan_1 <- KS_PUT
dirmngr[18085.1] DBG: chan_1 -> INQUIRE KEYBLOCK
dirmngr[18085.1] DBG: chan_1 <- [ 44 20 99 04 ae 04 49 51 0e 82 11 0c 00
95 6d aa ...(982 byte(s) skipped) ]
(...)
dirmngr[18085.1] DBG: chan_1 <- [ 44 20 2f 6f e7 d2 86 c8 53 cb 7d ed d4
75 7f 32 ...(709 byte(s) skipped) ]
dirmngr[18085.1] DBG: chan_1 <- END
dirmngr[18085.1] DBG: chan_1 -> INQUIRE KEYBLOCK_INFO
dirmngr[18085.1] DBG: chan_1 <- D pub:5A1796454623BA84
(...)
dirmngr[18085.1] DBG: chan_1 <- END
dirmngr[18085.1] getnameinfo returned for
'hkps.pool.sks-keyservers.net': 'hkps.pool.sks-keyservers.net' [already
known]
dirmngr[18085.1] DBG: chan_1 -> S PROGRESS tick ? 0 0
dirmngr[18085.1] DBG: chan_1 -> OK
dirmngr[18085.0] DBG: chan_0 <- [eof]
dirmngr[18085.0] Handhabungsroutine für den fd 0 beendet
dirmngr[18085.1] DBG: chan_1 <- BYE
dirmngr[18085.1] DBG: chan_1 -> OK closing connection
dirmngr[18085.1] Handhabungsroutine für den fd 1 beendet
dirmngr[18085.0] starting housekeeping
dirmngr[18085.0] ready with housekeeping


-- 
Ciao
Kai

http://kairaven.de/

___
Gnupg-users mailing list
Gnupg-users@gnupg.org
http://lists.gnupg.org/mailman/listinfo/gnupg-users

Re: 2.x

[K. Raven]

Hi,

> On Sa, Dez 21 2013, Uwe Brauer wrote:
> 
>> I am on Kubuntu 10.04 and I have both gnupg and gnupg2 installed.
>> Now since 2.x is not affected by the problem mentioned I prefer to
>> use it. However how can I be sure that gnupg2 is used for my email 
>> correspondence for which I use pgp-mime and not gnupg? (I am using 
>> Xemacs+gnus)
> 
> You can uninstall or update gnupg :-)

I'm using Kubuntu (13.10) too and because many packets depend on gnupg,
i use the Alternatives system to leave gnupg1 installed and use gnupg2
in parallel. You can see that on
 (in German, but
the commandos are readable). Sure, you must repeat the steps after gnupg
updates. Alternatively (at the end of the chapter), you can rename the
gnupg1 binaries and make symlinks to gnupg2, but i don't like that.

-- 
Ciao
Kai

http://kairaven.de/

___
Gnupg-users mailing list
Gnupg-users@gnupg.org
http://lists.gnupg.org/mailman/listinfo/gnupg-users