gpgsm not asking dirmngr for trusted root ca

[Bernhard Reiter]

Am Montag, 28. Juni 2010 14:35:45 schrieb Bernhard Reiter:
> If dirmngr trusts a root ca, wouldn't it be cool
> if the gpgsm (or gpg-agent) could also use that information?

And if you want to check my signature on that email, here is the diff
to fix that mailman issue:

--- gpgsm not asking dirmngr for trusted root ca.mbox   2010-06-28 
17:26:08.680510851 +0200
+++ repaired.mbox       2010-06-28 17:37:57.496508084 +0200
@@ -176,3 +176,4 @@
 --Boundary-01=_icJKMwp0j0mE9Cu
-Content-Type: application/x-x509-ca-cert; name="intevation-email-ca-2010.pem"
+Content-Type: application/x-x509-ca-cert;
+  name="intevation-email-ca-2010.pem"
 Content-Transfer-Encoding: 7bit

> While doing some tests today, I stumbled over the issue
> and that it is way to hard to maintain an installation wide root ca list.
>
> I suggest that
> a) "include-default" for the personal trustlist.txt is the default.
>     So we might need to come up with "
> b) "include-default" somehow also uses the dirmngr trusted-certs/.
> c) gpg-agent should also use GNUPGHOME (at least for me it does not seem to
> do it. But I might have make a mistake.)
> d) The documentation is fixed
>    info gpgsm Installation



-- 
Managing Director - Owner: www.intevation.net       (Free Software Company)
Deputy Coordinator Germany: fsfe.org. Board member: www.kolabsys.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: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part.
URL: </pipermail/attachments/20100628/4086a07e/attachment.pgp>