empty trust field for --with-colons and CMS

Bernhard Reiter bernhard at intevation.de
Wed Aug 13 14:16:16 CEST 2008

What does an empty second field for "crt" and "uid" --with-colons mean?

Current documentation
does not seem to have a hint about this.

My problem is that I do get an extra warning when trying to encrypt
with a gpgme using application (Kontact enterprise35, see 
compare kolab/issue2976 (Irritating trust warning when selecting keys for 

On the command line encryption works fine as it should.
The root cert is in there an trusted, also all CRLs are fine,

LANG=C gpgsm --with-colons --list-keys bernhard at intevation.de
BUG: trying to release an already released cert
8,O=Intevation GmbH,C=DE::escESC:
uid:::::::::CN=Bernhard Reiter,O=Intevation GmbH,C=DE::
uid:::::::::<bernhard at intevation.de>::
secmem usage: 0/16384 bytes in 0 blocks

The empty field seems to be undefined.
Gpgme will interpret this as  GPGME_VALIDITY_UNKNOWN   = 0.
It looks incorrect to me.
What am I missing?

Managing Director - Owner: www.intevation.net       (Free Software Company)
Germany Coordinator: fsfeurope.org. Coordinator: www.Kolab-Konsortium.com.
Intevation GmbH, Osnabrück, DE; Amtsgericht Osnabrück, HRB 18998
Geschäftsführer Frank Koormann, Bernhard Reiter, Dr. Jan-Oliver Wagner
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 1603 bytes
Desc: not available
URL: </pipermail/attachments/20080813/f908810b/attachment.bin>

More information about the Gnupg-devel mailing list