From wk at gnupg.org Wed Jan 2 09:29:25 2008 From: wk at gnupg.org (Werner Koch) Date: Wed, 02 Jan 2008 09:29:25 +0100 Subject: logger-file vs log-file options (gnupg-2 regression?) In-Reply-To: <9e0cf0bf0712291232s1636caa7y93aa8b7778ea4325@mail.gmail.com> (Alon Bar-Lev's message of "Sat, 29 Dec 2007 22:32:57 +0200") References: <9e0cf0bf0712291232s1636caa7y93aa8b7778ea4325@mail.gmail.com> Message-ID: <87k5msmxzu.fsf@wheatstone.g10code.de> On Sat, 29 Dec 2007 21:32, alon.barlev at gmail.com said: > The logger-file was changed to log-file in gnupg-2. The other way around: gnupg-2: 2004-03-23 Werner Koch * g10.c: New options --gpgconf-list, --debug-level and --log-file gnupg-1: 2004-11-17 Werner Koch * g10.c (open_info_file): New. (main): Unconditionally implement --status-file, --logger-file, > The man page continue to document logger-file. I'll fix the man page and add an --logger-file alias. Shalom-Salam, Werner -- Die Gedanken sind frei. Auschnahme regelt ein Bundeschgesetz. From wk at gnupg.org Wed Jan 2 09:35:27 2008 From: wk at gnupg.org (Werner Koch) Date: Wed, 02 Jan 2008 09:35:27 +0100 Subject: compiling GnuPG for x86_64-pc-mingw32 In-Reply-To: <477828DC.8050601@idirect.com> (Tom Pegios's message of "Sun, 30 Dec 2007 18:25:16 -0500") References: <477828DC.8050601@idirect.com> Message-ID: <87fxxgmxps.fsf@wheatstone.g10code.de> On Mon, 31 Dec 2007 00:25, tomp at idirect.com said: > The x86_64-pc-mingw32 (64-bit) version of GnuPG can be built on MSYS > now but requires 2 changes to the source code. We don't support building on a native Windows platform. > If these 2 changes can be included in GnuPG this will allow for a > successful 64-bit build under windows without any file modifications. As soon as the mingw cross compiling kit on Debian requires this change it will be added. For the time being, please maintain your own patch. Salam-Shalom, Werner -- Die Gedanken sind frei. Auschnahme regelt ein Bundeschgesetz. From bernhard at intevation.de Wed Jan 2 12:34:42 2008 From: bernhard at intevation.de (Bernhard Reiter) Date: Wed, 2 Jan 2008 12:34:42 +0100 Subject: import of external certificates via command line In-Reply-To: <87ir2synyj.fsf@wheatstone.g10code.de> References: <200710122324.45353.jan-oliver.wagner@intevation.de> <200712211715.17932.bernhard@intevation.de> <87ir2synyj.fsf@wheatstone.g10code.de> Message-ID: <200801021234.46115.bernhard@intevation.de> On Friday 21 December 2007 18:09, Werner Koch wrote: > On Fri, 21 Dec 2007 17:15, bernhard at intevation.de said: > > No it does not give me the key, only the attributes. > > You may then use the listed fingerprint to export the key. ?Note that > you must use the fingerprint, the keyid is wrong and the issuer DN is > definitely wrong; only the fingerprint is ... Okay, the procedure as far as I know is: gpgsm --list-external-keys Boromir # select the fingerprint from the listing gpgsm --export b0:12:12:..... >boromirskey gpgsm --import boromirskey (tested with gpgsm 2.0.7) This is confusing, because gpgsm --export Boromir will _not_ work, even when there is only one key found. also this cannot be learned from the documentation and thus is obscure. Bernhard -- 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: 1571 bytes Desc: not available URL: From wk at gnupg.org Wed Jan 2 13:37:00 2008 From: wk at gnupg.org (Werner Koch) Date: Wed, 02 Jan 2008 13:37:00 +0100 Subject: import of external certificates via command line In-Reply-To: <200801021234.46115.bernhard@intevation.de> (Bernhard Reiter's message of "Wed, 2 Jan 2008 12:34:42 +0100") References: <200710122324.45353.jan-oliver.wagner@intevation.de> <200712211715.17932.bernhard@intevation.de> <87ir2synyj.fsf@wheatstone.g10code.de> <200801021234.46115.bernhard@intevation.de> Message-ID: <877iisl7yr.fsf@wheatstone.g10code.de> On Wed, 2 Jan 2008 12:34, bernhard at intevation.de said: > This is confusing, because > gpgsm --export Boromir > will _not_ work, even when there is only one key found. > also this cannot be learned from the documentation and thus is obscure. We have similar thing in gpg for many years. Only the fingerprint unambiguously indentifies a key and thus we use this hack to also export those hidden certificates. That feature has been implemented on request from the KMail/Kleopatra folks. It is not documented because it is indeed obscure ;-). Shalom-Salam, Werner -- Die Gedanken sind frei. Auschnahme regelt ein Bundeschgesetz. From bernhard at intevation.de Wed Jan 2 13:41:22 2008 From: bernhard at intevation.de (Bernhard Reiter) Date: Wed, 2 Jan 2008 13:41:22 +0100 Subject: exporting and importing some subkeys Message-ID: <200801021341.28169.bernhard@intevation.de> With gnupg 2.0.7 (and 2.0.5): Given two machines with .gnupg having your secret key and doing "addkey" on one, I encountered a problem trying to transfer the new subkey to the other. gpg2 --export-secret-key ABCDEF >mykey worked even when ABCDEF is the fingerprint of my new subkey. gpg2 --import mykey tells me that the key is already in my keyring. gpg2 --list-secret-keys does not have the new subkey, so I guess the problem to be in the import. Am I missing something? Bernhard -- 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: not available Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From bernhard at intevation.de Wed Jan 2 13:43:16 2008 From: bernhard at intevation.de (Bernhard Reiter) Date: Wed, 2 Jan 2008 13:43:16 +0100 Subject: documentation: list format explained? Message-ID: <200801021343.17027.bernhard@intevation.de> Is there a section in the documentation which explains the different attributes of a key listing, e.g. in --edit --list-keys --list-secret keys? I have grepped for "ssb" and did not find it in the info source. Such a documentation would be very useful. Bernhard -- 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: not available Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From bernhard at intevation.de Wed Jan 2 14:18:45 2008 From: bernhard at intevation.de (Bernhard Reiter) Date: Wed, 2 Jan 2008 14:18:45 +0100 Subject: import of external certificates via command line In-Reply-To: <877iisl7yr.fsf@wheatstone.g10code.de> References: <200710122324.45353.jan-oliver.wagner@intevation.de> <200801021234.46115.bernhard@intevation.de> <877iisl7yr.fsf@wheatstone.g10code.de> Message-ID: <200801021418.46928.bernhard@intevation.de> On Wednesday 02 January 2008 13:37, Werner Koch wrote: > On Wed, ?2 Jan 2008 12:34, bernhard at intevation.de said: > > This is confusing, because > > ??????gpgsm --export Boromir > > ??????will _not_ work, even when there is only one key found. > > also this cannot be learned from the documentation and thus is obscure. > > We have similar thing in gpg for many years. ?Only the fingerprint > unambiguously indentifies a key and thus we use this hack to also export > those hidden certificates. ?That feature has been implemented on request > from the KMail/Kleopatra folks. Well, it is good to at least have a method. > It is not documented because it is indeed obscure ;-). To have a way to import externally found certificates is a feature that people are missing. So why not document the current way until a better one is implemented. Bernhard -- 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: not available Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From wk at gnupg.org Wed Jan 2 15:20:24 2008 From: wk at gnupg.org (Werner Koch) Date: Wed, 02 Jan 2008 15:20:24 +0100 Subject: documentation: list format explained? In-Reply-To: <200801021343.17027.bernhard@intevation.de> (Bernhard Reiter's message of "Wed, 2 Jan 2008 13:43:16 +0100") References: <200801021343.17027.bernhard@intevation.de> Message-ID: <874pdwjolz.fsf@wheatstone.g10code.de> On Wed, 2 Jan 2008 13:43, bernhard at intevation.de said: > I have grepped for "ssb" and did not find it in the info source. > Such a documentation would be very useful. gnupg/doc/DETAILS 1. Field: Type of record pub = public key crt = X.509 certificate crs = X.509 certificate and private key available sub = subkey (secondary key) sec = secret key ssb = secret subkey (secondary key) uid = user id (only field 10 is used). uat = user attribute (same as user id except for field 10). sig = signature rev = revocation signature fpr = fingerprint: (fingerprint is in field 10) pkd = public key data (special field format, see below) grp = reserved for gpgsm rvk = revocation key tru = trust database information spk = signature subpacket [...] Shalom-Salam, Werner -- Die Gedanken sind frei. Auschnahme regelt ein Bundeschgesetz. From wk at gnupg.org Wed Jan 2 15:22:13 2008 From: wk at gnupg.org (Werner Koch) Date: Wed, 02 Jan 2008 15:22:13 +0100 Subject: import of external certificates via command line In-Reply-To: <200801021418.46928.bernhard@intevation.de> (Bernhard Reiter's message of "Wed, 2 Jan 2008 14:18:45 +0100") References: <200710122324.45353.jan-oliver.wagner@intevation.de> <200801021234.46115.bernhard@intevation.de> <877iisl7yr.fsf@wheatstone.g10code.de> <200801021418.46928.bernhard@intevation.de> Message-ID: <87zlvoi9yi.fsf@wheatstone.g10code.de> On Wed, 2 Jan 2008 14:18, bernhard at intevation.de said: > To have a way to import externally found certificates > is a feature that people are missing. So why not document the current > way until a better one is implemented. We don't document obscure features because these makes it a bit easier for us to change the semantics. Salam-Shalom, Werner -- Die Gedanken sind frei. Auschnahme regelt ein Bundeschgesetz. From alon.barlev at gmail.com Wed Jan 2 15:29:18 2008 From: alon.barlev at gmail.com (Alon Bar-Lev) Date: Wed, 2 Jan 2008 16:29:18 +0200 Subject: logger-file vs log-file options (gnupg-2 regression?) In-Reply-To: <87k5msmxzu.fsf@wheatstone.g10code.de> References: <9e0cf0bf0712291232s1636caa7y93aa8b7778ea4325@mail.gmail.com> <87k5msmxzu.fsf@wheatstone.g10code.de> Message-ID: <9e0cf0bf0801020629q37aa8a98q468b222f883d4df5@mail.gmail.com> Thanks, Any reason to break the parameter compatibility between the two versions? --logger-file does not work anymore. Alon. On 1/2/08, Werner Koch wrote: > On Sat, 29 Dec 2007 21:32, alon.barlev at gmail.com said: > > > The logger-file was changed to log-file in gnupg-2. > > The other way around: > > gnupg-2: > > 2004-03-23 Werner Koch > > * g10.c: New options --gpgconf-list, --debug-level and --log-file > > gnupg-1: > > 2004-11-17 Werner Koch > > * g10.c (open_info_file): New. > (main): Unconditionally implement --status-file, --logger-file, > > > The man page continue to document logger-file. > > I'll fix the man page and add an --logger-file alias. > > > Shalom-Salam, > > Werner > > -- > Die Gedanken sind frei. Auschnahme regelt ein Bundeschgesetz. > > From bernhard at intevation.de Wed Jan 2 16:20:01 2008 From: bernhard at intevation.de (Bernhard Reiter) Date: Wed, 2 Jan 2008 16:20:01 +0100 Subject: import of external certificates via command line In-Reply-To: <87zlvoi9yi.fsf@wheatstone.g10code.de> References: <200710122324.45353.jan-oliver.wagner@intevation.de> <200801021418.46928.bernhard@intevation.de> <87zlvoi9yi.fsf@wheatstone.g10code.de> Message-ID: <200801021620.05062.bernhard@intevation.de> On Wednesday 02 January 2008 15:22, Werner Koch wrote: > On Wed, ?2 Jan 2008 14:18, bernhard at intevation.de said: > > To have a way to import externally found certificates > > is a feature that people are missing. So why not document the current > > way until a better one is implemented. > > We don't document obscure features because these makes it a bit easier > for us to change the semantics. Werner, somehow I feel you are weaseling around the problem... It is a _non_ obscure problem that you cannot import an externally found certificate. Lack of mentioning this use case in the documentation does irritate an advanced user. You can a) fix the problem and add some option to gpgsm and the documentation so that the use case is possible b) mention the dirty workaround somewhere, maybe declare it and its semantics dirty. Doing b) is not very time intensive and will help Gnupg's quality, which is something I have learned by user feedback and my own experiences. I hope this feedback is welcome. Best, Bernhard -- 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: 1571 bytes Desc: not available URL: From bernhard at intevation.de Wed Jan 2 16:23:01 2008 From: bernhard at intevation.de (Bernhard Reiter) Date: Wed, 2 Jan 2008 16:23:01 +0100 Subject: documentation: list format explained? In-Reply-To: <874pdwjolz.fsf@wheatstone.g10code.de> References: <200801021343.17027.bernhard@intevation.de> <874pdwjolz.fsf@wheatstone.g10code.de> Message-ID: <200801021623.05604.bernhard@intevation.de> On Wednesday 02 January 2008 15:20, Werner Koch wrote: > > I have grepped for "ssb" and did not find it in the info source. > > Such a documentation would be very useful. > > gnupg/doc/DETAILS Ah! Thanks for the hint! I suggest to add a similiar hint towards the file in the gnupg2.info* files. > ?1. Field: ?Type of record > ???????? ? ?pub = public key > ? ? ? ? ? ? crt = X.509 certificate > ? ? ? ? ? ? crs = X.509 certificate and private key available > ???????? ? ?sub = subkey (secondary key) > ???????? ? ?sec = secret key > ???????? ? ?ssb = secret subkey (secondary key) -- 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: not available Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From wk at gnupg.org Wed Jan 2 16:56:25 2008 From: wk at gnupg.org (Werner Koch) Date: Wed, 02 Jan 2008 16:56:25 +0100 Subject: import of external certificates via command line In-Reply-To: <200801021620.05062.bernhard@intevation.de> (Bernhard Reiter's message of "Wed, 2 Jan 2008 16:20:01 +0100") References: <200710122324.45353.jan-oliver.wagner@intevation.de> <200801021418.46928.bernhard@intevation.de> <87zlvoi9yi.fsf@wheatstone.g10code.de> <200801021620.05062.bernhard@intevation.de> Message-ID: <87sl1ggr12.fsf@wheatstone.g10code.de> On Wed, 2 Jan 2008 16:20, bernhard at intevation.de said: > somehow I feel you are weaseling around the problem... No. Before you can even run an external search you need to configure the dirmngr to *your* local environment. There is no universal way to find X.509 certificates - it highly depends on the concrete PKI! This is very different from PGP where it is common to store keys on the synced network of keyservers. All real world X.509 PKIs provide a custom way to lookup certificates - in general you need to use this custom method. Further, there is never a need to lookup certificates *if* the PKI is proper working. gpgsm will do this for you then. If we start to document how to get certifcates from certain PKIs we will soon end up with a large howto on how the PKIs all over the world are misconfigured and how to solve each of the problems. This is not the job of a general purpose software. Salam-Shalom, Werner -- Die Gedanken sind frei. Auschnahme regelt ein Bundeschgesetz. From wk at gnupg.org Wed Jan 2 17:01:33 2008 From: wk at gnupg.org (Werner Koch) Date: Wed, 02 Jan 2008 17:01:33 +0100 Subject: logger-file vs log-file options (gnupg-2 regression?) In-Reply-To: <9e0cf0bf0801020629q37aa8a98q468b222f883d4df5@mail.gmail.com> (Alon Bar-Lev's message of "Wed, 2 Jan 2008 16:29:18 +0200") References: <9e0cf0bf0712291232s1636caa7y93aa8b7778ea4325@mail.gmail.com> <87k5msmxzu.fsf@wheatstone.g10code.de> <9e0cf0bf0801020629q37aa8a98q468b222f883d4df5@mail.gmail.com> Message-ID: <87odc4gqsi.fsf@wheatstone.g10code.de> On Wed, 2 Jan 2008 15:29, alon.barlev at gmail.com said: > Any reason to break the parameter compatibility between the two versions? > --logger-file does not work anymore. There has never been a --logger-file for gpg2. There is a --log-file and we only later added --logger-file to gpg-1. That is a bit unfortunate but that is a fact for 3 years. Also see: >> I'll fix the man page and add an --logger-file alias. .. to gpg2. Shalom-Salam, Werner -- Die Gedanken sind frei. Auschnahme regelt ein Bundeschgesetz. From wk at gnupg.org Wed Jan 2 17:04:07 2008 From: wk at gnupg.org (Werner Koch) Date: Wed, 02 Jan 2008 17:04:07 +0100 Subject: logger-file vs log-file options (gnupg-2 regression?) In-Reply-To: <9e0cf0bf0801020629q37aa8a98q468b222f883d4df5@mail.gmail.com> (Alon Bar-Lev's message of "Wed, 2 Jan 2008 16:29:18 +0200") References: <9e0cf0bf0712291232s1636caa7y93aa8b7778ea4325@mail.gmail.com> <87k5msmxzu.fsf@wheatstone.g10code.de> <9e0cf0bf0801020629q37aa8a98q468b222f883d4df5@mail.gmail.com> Message-ID: <87k5msgqo8.fsf@wheatstone.g10code.de> Hi, FWIW, I just recall why we have different names: --log-file allows for a special name "socket:///fooo" whereas --logger-file does not. Salam-Shalom, Werner -- Die Gedanken sind frei. Auschnahme regelt ein Bundeschgesetz. From marcus.brinkmann at ruhr-uni-bochum.de Wed Jan 2 17:10:19 2008 From: marcus.brinkmann at ruhr-uni-bochum.de (Marcus Brinkmann) Date: Wed, 02 Jan 2008 17:10:19 +0100 Subject: Frontend for GPG In-Reply-To: <200712211048.25215.bernhard@intevation.de> References: <3ac86fa70712111623wd83e701vd07440a6966dde65@mail.gmail.com> <200712211048.25215.bernhard@intevation.de> Message-ID: <87sl1g5huc.wl%marcus.brinkmann@ruhr-uni-bochum.de> At Fri, 21 Dec 2007 10:48:24 +0100, Bernhard Reiter wrote: > > [1 ] > [1.1 ] > On Wednesday 12 December 2007 01:23, Brad Tilley wrote: > > Are there any docs that describe a programmatic > > interface to gpg or how to go about this sort of thing with a > > os.system and/or os.popen library? > > The canonical way would be to use gpgme, > but of course this might already have to many feature for your use case. > It would be cool to have python gpgme bindings. http://pyme.sourceforge.net/ Thanks, Marcus From bernhard at intevation.de Wed Jan 2 18:01:08 2008 From: bernhard at intevation.de (Bernhard Reiter) Date: Wed, 2 Jan 2008 18:01:08 +0100 Subject: import of external certificates via command line In-Reply-To: <87sl1ggr12.fsf@wheatstone.g10code.de> References: <200710122324.45353.jan-oliver.wagner@intevation.de> <200801021620.05062.bernhard@intevation.de> <87sl1ggr12.fsf@wheatstone.g10code.de> Message-ID: <200801021801.13105.bernhard@intevation.de> On Wednesday 02 January 2008 16:56, Werner Koch wrote: > On Wed, ?2 Jan 2008 16:20, bernhard at intevation.de said: > > somehow I feel you are weaseling around the problem... > > No. ?Before you can even run an external search you need to configure > the dirmngr to *your* local environment. But when my external search is working, why can't I get those certificates right away? > ? ?There is no universal way to find X.509 certificates - it highly > ? ?depends on the concrete PKI! > > This is very different from PGP where it is common to store keys on the > synced network of keyservers. ?All real world X.509 PKIs provide a > custom way to lookup certificates - in general you need to use this > custom method. In Germany I know the Bavarian one which responds to ldap searches. There will always be keys that I do not have in my personal keybox but I can find by other means. All I want is a way to get these keys into my person keybox when I can already find them. > Further, there is never a need to lookup certificates *if* the PKI is > proper working. ?gpgsm will do this for you then. ? You sound like locally saved keys were a bad design idea. > If we start to > document how to get certifcates from certain PKIs we will soon end up > with a large howto on how the PKIs all over the world are misconfigured > and how to solve each of the problems. ?This is not the job of a general > purpose software. The purpose of a general purpose software is to be practical and if there a major PKIs which "special" in different ways it might be practical to support them so that the software is interoperable and useful. However this is not the point. There are directory services you can ask by LDAP which have reserved attributes for public keys. Gpgsm needs to be able to handle LDAP anyway, thus doing external searches for these directory services seem to be quite sensible to me. So why not import the found keys?? Bernhard -- 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: not available Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From bernhard at intevation.de Wed Jan 2 18:06:17 2008 From: bernhard at intevation.de (Bernhard Reiter) Date: Wed, 2 Jan 2008 18:06:17 +0100 Subject: pyme (was: Frontend for GPG) In-Reply-To: <87sl1g5huc.wl%marcus.brinkmann@ruhr-uni-bochum.de> References: <3ac86fa70712111623wd83e701vd07440a6966dde65@mail.gmail.com> <200712211048.25215.bernhard@intevation.de> <87sl1g5huc.wl%marcus.brinkmann@ruhr-uni-bochum.de> Message-ID: <200801021806.18508.bernhard@intevation.de> On Wednesday 02 January 2008 17:10, Marcus Brinkmann wrote: > > It would be cool to have python gpgme bindings. > > http://pyme.sourceforge.net/ This looks abandoned, lowlevel and is based on SWIG. Nevertheless it could be a start. -- 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: not available Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From wk at gnupg.org Wed Jan 2 18:19:15 2008 From: wk at gnupg.org (Werner Koch) Date: Wed, 02 Jan 2008 18:19:15 +0100 Subject: import of external certificates via command line In-Reply-To: <200801021801.13105.bernhard@intevation.de> (Bernhard Reiter's message of "Wed, 2 Jan 2008 18:01:08 +0100") References: <200710122324.45353.jan-oliver.wagner@intevation.de> <200801021620.05062.bernhard@intevation.de> <87sl1ggr12.fsf@wheatstone.g10code.de> <200801021801.13105.bernhard@intevation.de> Message-ID: <874pdwf8mk.fsf@wheatstone.g10code.de> On Wed, 2 Jan 2008 18:01, bernhard at intevation.de said: > But when my external search is working, why can't I get those certificates > right away? Because certificates are so often broken and will mess up the certificates you already have. Importing all certifcates available is a bad idea and only needed if the PKI is broken - if it is broken tehre is a good chance that everything gets messed up. > In Germany I know the Bavarian one which responds to ldap searches. > There will always be keys that I do not have in my personal keybox > but I can find by other means. I usually have to resort to a general LDAP browser to locate a specific certificate, The automatic mode works only with proper administered LDAP directies (like the one you are running). > You sound like locally saved keys were a bad design idea. I did not say this. > However this is not the point. There are directory services you can ask by > LDAP which have reserved attributes for public keys. Gpgsm needs to be able Tell me this attribute! There is no standard for it and thus everyone is using a different one. See also "retrieving a certificate by serial number and issuer name" (which is not possible). Salam-Shalom, Werner -- Die Gedanken sind frei. Auschnahme regelt ein Bundeschgesetz. From alon.barlev at gmail.com Wed Jan 2 17:10:35 2008 From: alon.barlev at gmail.com (Alon Bar-Lev) Date: Wed, 2 Jan 2008 18:10:35 +0200 Subject: logger-file vs log-file options (gnupg-2 regression?) In-Reply-To: <87k5msgqo8.fsf@wheatstone.g10code.de> References: <9e0cf0bf0712291232s1636caa7y93aa8b7778ea4325@mail.gmail.com> <87k5msmxzu.fsf@wheatstone.g10code.de> <9e0cf0bf0801020629q37aa8a98q468b222f883d4df5@mail.gmail.com> <87k5msgqo8.fsf@wheatstone.g10code.de> Message-ID: <9e0cf0bf0801020810y4d519ac1v77933a744ac81132@mail.gmail.com> On 1/2/08, Werner Koch wrote: > FWIW, I just recall why we have different names: --log-file allows for a > special name "socket:///fooo" whereas --logger-file does not. Oh... So we can forget about having the same arguments for both versions? [[ Now I understand that is "alias" ]] Alon. From lofi at freebsd.org Wed Jan 2 20:45:43 2008 From: lofi at freebsd.org (Michael Nottebrock) Date: Wed, 02 Jan 2008 20:45:43 +0100 Subject: dirmngr-1.0.1 needs explicit libiconv dependency for --disable-nls case Message-ID: <477BE9E7.7070101@freebsd.org> See subject. Patch similar to the one found in the attachment to http://www.freebsd.org/cgi/query-pr.cgi?pr=119016 should fix the problem. Cheers, -- ,_, | Michael Nottebrock | lofi at freebsd.org (/^ ^\) | FreeBSD - The Power to Serve | http://www.freebsd.org \u/ | K Desktop Environment on FreeBSD | http://freebsd.kde.org -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 250 bytes Desc: OpenPGP digital signature URL: From marcus.brinkmann at ruhr-uni-bochum.de Wed Jan 2 23:32:28 2008 From: marcus.brinkmann at ruhr-uni-bochum.de (Marcus Brinkmann) Date: Wed, 02 Jan 2008 23:32:28 +0100 Subject: dirmngr-1.0.1 needs explicit libiconv dependency for --disable-nls case In-Reply-To: <477BE9E7.7070101@freebsd.org> References: <477BE9E7.7070101@freebsd.org> Message-ID: <87odc36epv.wl%marcus.brinkmann@ruhr-uni-bochum.de> At Wed, 02 Jan 2008 20:45:43 +0100, Michael Nottebrock wrote: > > [1 ] > [1.1 ] > See subject. > > Patch similar to the one found in the attachment to > http://www.freebsd.org/cgi/query-pr.cgi?pr=119016 should fix the problem. Checked in, thank you! 2008-01-02 Marcus Brinkmann * Makefile.am (dirmngr_LDADD, dirmngr_ldap_LDADD, (dirmngr_client_LDADD): Add $(LIBICONV). Reported by Michael Nottebrock. Marcus -- g10 Code GmbH http://g10code.com AmtsGer. Wuppertal HRB 14459 H?ttenstr. 61 Gesch?ftsf?hrung Werner Koch D-40699 Erkrath -=- The GnuPG Experts -=- USt-Id DE215605608 From bernhard at intevation.de Wed Jan 2 23:41:03 2008 From: bernhard at intevation.de (Bernhard Reiter) Date: Wed, 2 Jan 2008 23:41:03 +0100 Subject: import of external certificates via command line In-Reply-To: <874pdwf8mk.fsf@wheatstone.g10code.de> References: <200710122324.45353.jan-oliver.wagner@intevation.de> <200801021801.13105.bernhard@intevation.de> <874pdwf8mk.fsf@wheatstone.g10code.de> Message-ID: <200801022341.07949.bernhard@intevation.de> On Wednesday 02 January 2008 18:19, Werner Koch wrote: > On Wed, 2 Jan 2008 18:01, bernhard at intevation.de said: > > But when my external search is working, why can't I get those > > certificates right away? > > Because certificates are so often broken and will mess up the > certificates you already have. Importing all certifcates available is a > bad idea and only needed if the PKI is broken - if it is broken tehre is > a good chance that everything gets messed up. I am the whole thread writing about importing a subset of certificates that I have found by (possibly several) external searches, aka gpgsm --list-external-keys Frodo gpgsm --list-external-keys Sam ah, found, now gpgsm --with-import-please --list-external-keys Sam > > In Germany I know the Bavarian one which responds to ldap searches. > > There will always be keys that I do not have in my personal keybox > > but I can find by other means. > > I usually have to resort to a general LDAP browser to locate a specific > certificate, The automatic mode works only with proper administered LDAP > directies (like the one you are running). I have encountered a few now, ca.intevation.de, the Bavarian, ... And no matter how broken a directory service is, if --list-external-keys already found the certificiate, no matter where, it is completely beyond me, what there should not a command which will "import" this special subset of possible keys. > > You sound like locally saved keys were a bad design idea. > > I did not say this. You have said that a properly administered PKI would be able to locate the certificate you need anyway and used this argument to not add a special options to be able to important a selected group of externally found keys. I do not believe the argument because it is defeated by our own design which already (rightfully) takes into account existing PKIs. > > However this is not the point. There are directory services you can ask > > by LDAP which have reserved attributes for public keys. Gpgsm needs to be > > able > > Tell me this attribute! There is no standard for it and thus everyone > is using a different one. See also "retrieving a certificate by serial > number and issuer name" (which is not possible). http://tools.ietf.org/html/rfc4523 as 4.1. userCertificate The userCertificate attribute holds the X.509 certificates issued to the user by one or more certificate authorities, as discussed in clause 11.2.1 of [X.509]. ( 2.5.4.36 NAME 'userCertificate' DESC 'X.509 user certificate' EQUALITY certificateExactMatch SYNTAX 1.3.6.1.4.1.1466.115.121.1.8 ) It is reasonable to try this attribute when using the light weight database protocol. Bernhard -- 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: not available Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From patrick at mozilla-enigmail.org Wed Jan 2 23:01:55 2008 From: patrick at mozilla-enigmail.org (Patrick Brunschwig) Date: Wed, 02 Jan 2008 23:01:55 +0100 Subject: Status of GnuPG2 on Windows Message-ID: <477C09D3.3040504@mozilla-enigmail.org> What is the current status of GnuPG 2.0 on Windows. In the "What's New" section of the 2.0.8 release, I read that Windows is now a supported platform. Does that mean that GnuPG 2 is now considered stable on Windows, or just that it basically works? Thanks, Patrick From wk at gnupg.org Thu Jan 3 10:51:50 2008 From: wk at gnupg.org (Werner Koch) Date: Thu, 03 Jan 2008 10:51:50 +0100 Subject: Status of GnuPG2 on Windows In-Reply-To: <477C09D3.3040504@mozilla-enigmail.org> (Patrick Brunschwig's message of "Wed, 02 Jan 2008 23:01:55 +0100") References: <477C09D3.3040504@mozilla-enigmail.org> Message-ID: <87myrnck3t.fsf@wheatstone.g10code.de> On Wed, 2 Jan 2008 23:01, patrick at mozilla-enigmail.org said: > What is the current status of GnuPG 2.0 on Windows. In the "What's New" > section of the 2.0.8 release, I read that Windows is now a supported > platform. Does that mean that GnuPG 2 is now considered stable on > Windows, or just that it basically works? It is stable. Which does not mean that there are now bugs ;-). Shalom-Salam, Werner -- Die Gedanken sind frei. Auschnahme regelt ein Bundeschgesetz. From marcus.brinkmann at ruhr-uni-bochum.de Fri Jan 4 15:50:43 2008 From: marcus.brinkmann at ruhr-uni-bochum.de (Marcus Brinkmann) Date: Fri, 04 Jan 2008 15:50:43 +0100 Subject: [Announce] GPGME 1.1.6 released Message-ID: <874pdt4pbw.wl%marcus.brinkmann@ruhr-uni-bochum.de> Hi, We are pleased to announce version 1.1.6 of GnuPG Made Easy, a library designed to make access to GnuPG easier for applications. It may be found in the file (about 939 KB/730 KB compressed) ftp://ftp.gnupg.org/gcrypt/gpgme/gpgme-1.1.6.tar.gz ftp://ftp.gnupg.org/gcrypt/gpgme/gpgme-1.1.6.tar.bz2 The following files are also available: ftp://ftp.gnupg.org/gcrypt/gpgme/gpgme-1.1.6.tar.gz.sig ftp://ftp.gnupg.org/gcrypt/gpgme/gpgme-1.1.6.tar.bz2.sig ftp://ftp.gnupg.org/gcrypt/gpgme/gpgme-1.1.5-1.1.6.diff.gz It should soon appear on the mirrors listed at: http://www.gnupg.org/mirrors.html Bug reports and requests for assistance should be sent to: gnupg-devel at gnupg.org The sha1sum checksums for this distibution are ed2c9699367d1be32f84bf154673becd16deba0a gpgme-1.1.5-1.1.6.diff.gz 05218df939d72c2fd6d74f22c2b5d5ade0718b7a gpgme-1.1.6.tar.bz2 2c2994d98ab545d1bced14c0554f4a50fd8e0878 gpgme-1.1.6.tar.bz2.sig 8dee551f362fc428c25c9bd542ce944ac916347d gpgme-1.1.6.tar.gz 996e0b48a4f5e0ce3029e95c310ae64af92a6131 gpgme-1.1.6.tar.gz.sig Noteworthy changes in version 1.1.6 (2008-01-04) ------------------------------------------------ * Bug fixes for for W32. * A new, experimental (and thus undocumented and potentially unstable) interface for accessing gpg-conf through GPGME has been added. * Interface changes relative to the 1.1.1 release: ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ gpgme_signature_t EXTENDED: New field chain_model. gpgme_op_getauditlog_start NEW. gpgme_op_getauditlog NEW. GPGME_AUDITLOG_HTML NEW. GPGME_AUDITLOG_WITH_HELP NEW. Marcus Brinkmann mb at g10code.de -- g10 Code GmbH http://g10code.com AmtsGer. Wuppertal HRB 14459 H?ttenstr. 61 Gesch?ftsf?hrung Werner Koch D-40699 Erkrath -=- The GnuPG Experts -=- USt-Id DE215605608 _______________________________________________ Gnupg-announce mailing list Gnupg-announce at gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-announce From alon.barlev at gmail.com Fri Jan 4 16:45:16 2008 From: alon.barlev at gmail.com (Alon Bar-Lev) Date: Fri, 4 Jan 2008 17:45:16 +0200 Subject: [Announce] GPGME 1.1.6 released In-Reply-To: <874pdt4pbw.wl%marcus.brinkmann@ruhr-uni-bochum.de> References: <874pdt4pbw.wl%marcus.brinkmann@ruhr-uni-bochum.de> Message-ID: <9e0cf0bf0801040745v47141dbfkaf54ad97138bc59b@mail.gmail.com> On 1/4/08, Marcus Brinkmann wrote: > Hi, > > We are pleased to announce version 1.1.6 of GnuPG Made Easy, > a library designed to make access to GnuPG easier for applications. Hello, Please fix some qa issues. * QA Notice: Package has poor programming practices which may compile * fine but exhibit random runtime failures. * assuan-pipe-connect.c:593: warning: implicit declaration of function '_gpgme_io_pipe' assuan-pipe-connect.c:638: warning: implicit declaration of function '_gpgme_io_spawn' Attach is a temp fix, as including the priv-io.h conflict with other parts of the software. Also... One test fails: PASS: t-verify Hallo Leute! PASS: t-decrypt t-sign.c:107: KSBA: Not found (9.27) FAIL: t-sign Begin Result: Issuer ...: /CN=DFN Top Level Certification Authority/OU=DFN-PCA/O=Deutsches Forschungsnetz/C=DE/EMail=certify at pca.dfn.de Serial ...: 01 Subject ..: /CN=DFN Top Level Certification Authority/OU=DFN-PCA/O=Deutsches Forschungsnetz/C=DE/EMail=certify at pca.dfn.de During tests, the pinentry dialogs are shown, I must write "abc" for tests to run (many times), can you please make the test use silent passphrase? Best Regards, Alon Bar-Lev. -------------- next part -------------- A non-text attachment was scrubbed... Name: gpgme-1.1.6-qa.patch Type: text/x-diff Size: 580 bytes Desc: not available URL: From marcus.brinkmann at ruhr-uni-bochum.de Fri Jan 4 16:53:26 2008 From: marcus.brinkmann at ruhr-uni-bochum.de (Marcus Brinkmann) Date: Fri, 04 Jan 2008 16:53:26 +0100 Subject: [Announce] GPGME 1.1.6 released In-Reply-To: <9e0cf0bf0801040745v47141dbfkaf54ad97138bc59b@mail.gmail.com> References: <874pdt4pbw.wl%marcus.brinkmann@ruhr-uni-bochum.de> <9e0cf0bf0801040745v47141dbfkaf54ad97138bc59b@mail.gmail.com> Message-ID: <87wsqp37ux.wl%marcus.brinkmann@ruhr-uni-bochum.de> At Fri, 4 Jan 2008 17:45:16 +0200, "Alon Bar-Lev" wrote: > > [1 ] > On 1/4/08, Marcus Brinkmann wrote: > > Hi, > > > > We are pleased to announce version 1.1.6 of GnuPG Made Easy, > > a library designed to make access to GnuPG easier for applications. > > Hello, > > Please fix some qa issues. > * QA Notice: Package has poor programming practices which may compile > * fine but exhibit random runtime failures. > * assuan-pipe-connect.c:593: warning: implicit declaration of > function '_gpgme_io_pipe' > assuan-pipe-connect.c:638: warning: implicit declaration of function > '_gpgme_io_spawn' > > Attach is a temp fix, as including the priv-io.h conflict with other > parts of the software. The fix is fine, priv-io.h is not part of assuan, and thus repeating the internal declarations is good enough. > Also... One test fails: > > PASS: t-verify > Hallo Leute! > PASS: t-decrypt > t-sign.c:107: KSBA: Not found (9.27) > FAIL: t-sign > Begin Result: > Issuer ...: /CN=DFN Top Level Certification > Authority/OU=DFN-PCA/O=Deutsches > Forschungsnetz/C=DE/EMail=certify at pca.dfn.de > Serial ...: 01 > Subject ..: /CN=DFN Top Level Certification > Authority/OU=DFN-PCA/O=Deutsches > Forschungsnetz/C=DE/EMail=certify at pca.dfn.de Which version of gpgsm do you use? The tests run fine here. > During tests, the pinentry dialogs are shown, I must write "abc" for > tests to run (many times), can you please make the test use silent > passphrase? We already set GPG_AGENT_INFO to empty in the test environment (see TEST_ENVIRONMENT in tests/gpgsm/Makefile.am). I have no idea why this is not working for you. Did you run "make check" or invoked the test manually? Thanks, Marcus From alon.barlev at gmail.com Fri Jan 4 17:01:19 2008 From: alon.barlev at gmail.com (Alon Bar-Lev) Date: Fri, 4 Jan 2008 18:01:19 +0200 Subject: [Announce] GPGME 1.1.6 released In-Reply-To: <87wsqp37ux.wl%marcus.brinkmann@ruhr-uni-bochum.de> References: <874pdt4pbw.wl%marcus.brinkmann@ruhr-uni-bochum.de> <9e0cf0bf0801040745v47141dbfkaf54ad97138bc59b@mail.gmail.com> <87wsqp37ux.wl%marcus.brinkmann@ruhr-uni-bochum.de> Message-ID: <9e0cf0bf0801040801v7d372b72g2ca50efab827d579@mail.gmail.com> On 1/4/08, Marcus Brinkmann wrote: > The fix is fine, priv-io.h is not part of assuan, and thus repeating > the internal declarations is good enough. This is not so good practice... You can separate these into their own header file and include it from both places. > Which version of gpgsm do you use? The tests run fine here. $ gpgsm --version gpgsm (GnuPG) 2.0.8 Copyright (C) 2007 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Home: ~/.gnupg Supported algorithms: Cipher: 3DES, AES, AES192, AES256, SERPENT128, SERPENT192, SERPENT256, SEED, CAMELLIA128, CAMELLIA192, CAMELLIA256 Pubkey: RSA, ECDSA Hash: MD5, SHA1, RIPEMD160, SHA256, SHA384, SHA512, WHIRLPOOL Used libraries: gcrypt(1.4.0), ksba(1.0.2), assuan(1.0.4) > We already set GPG_AGENT_INFO to empty in the test environment (see > TEST_ENVIRONMENT in tests/gpgsm/Makefile.am). I have no idea why this > is not working for you. Did you run "make check" or invoked the test > manually? I use "make check". GPG_AGENT_INFO= echo alon | gpg2 --sign Will result in running an agent by itself... right? Alon. From marcus.brinkmann at ruhr-uni-bochum.de Fri Jan 4 17:24:27 2008 From: marcus.brinkmann at ruhr-uni-bochum.de (Marcus Brinkmann) Date: Fri, 04 Jan 2008 17:24:27 +0100 Subject: [Announce] GPGME 1.1.6 released In-Reply-To: <9e0cf0bf0801040801v7d372b72g2ca50efab827d579@mail.gmail.com> References: <874pdt4pbw.wl%marcus.brinkmann@ruhr-uni-bochum.de> <9e0cf0bf0801040745v47141dbfkaf54ad97138bc59b@mail.gmail.com> <87wsqp37ux.wl%marcus.brinkmann@ruhr-uni-bochum.de> <9e0cf0bf0801040801v7d372b72g2ca50efab827d579@mail.gmail.com> Message-ID: <87sl1d36f8.wl%marcus.brinkmann@ruhr-uni-bochum.de> At Fri, 4 Jan 2008 18:01:19 +0200, "Alon Bar-Lev" wrote: > > On 1/4/08, Marcus Brinkmann wrote: > > The fix is fine, priv-io.h is not part of assuan, and thus repeating > > the internal declarations is good enough. > > This is not so good practice... You can separate these into their own > header file and include it from both places. Sometimes even good practices need to be broken. This is such a case. There is a better solution, but it requires major extensions to libassuan, which we are not currently planning for (to be specific: libassuan should provide hooks for everything gpgme needs to change in its implementation. Then we can just link to libassuan and remove the local copy). > > Which version of gpgsm do you use? The tests run fine here. > > $ gpgsm --version > gpgsm (GnuPG) 2.0.8 Ok, I used 2.0.4 for testing the release. It is possible that something changed which broke the test case, I'll have to check it out. Thanks for letting me know. > > We already set GPG_AGENT_INFO to empty in the test environment (see > > TEST_ENVIRONMENT in tests/gpgsm/Makefile.am). I have no idea why this > > is not working for you. Did you run "make check" or invoked the test > > manually? > > I use "make check". Probably also related to the gpg/gpgsm version. > GPG_AGENT_INFO= echo alon | gpg2 --sign > > Will result in running an agent by itself... right? Mmh. Did you specify gpg2 as default gpg for gpgme? And did it ask for the passphrase in tests/gpg or tests/gpgsm? Actually, in which particular test, gpg/t-sign? Thanks, Marcus From alon.barlev at gmail.com Fri Jan 4 17:32:05 2008 From: alon.barlev at gmail.com (Alon Bar-Lev) Date: Fri, 4 Jan 2008 18:32:05 +0200 Subject: [Announce] GPGME 1.1.6 released In-Reply-To: <87sl1d36f8.wl%marcus.brinkmann@ruhr-uni-bochum.de> References: <874pdt4pbw.wl%marcus.brinkmann@ruhr-uni-bochum.de> <9e0cf0bf0801040745v47141dbfkaf54ad97138bc59b@mail.gmail.com> <87wsqp37ux.wl%marcus.brinkmann@ruhr-uni-bochum.de> <9e0cf0bf0801040801v7d372b72g2ca50efab827d579@mail.gmail.com> <87sl1d36f8.wl%marcus.brinkmann@ruhr-uni-bochum.de> Message-ID: <9e0cf0bf0801040832q45fa6929n7c071efbc0d26dd@mail.gmail.com> On 1/4/08, Marcus Brinkmann wrote: > Mmh. Did you specify gpg2 as default gpg for gpgme? And did it ask /usr/bin/gpg is link to /usr/bin/gpg2, gpgme configuration detect the correct version. > for the passphrase in tests/gpg or tests/gpgsm? Actually, in which > particular test, gpg/t-sign? make check-TESTS make[3]: Entering directory `/home/alonbl/tmp/xx/gpgme-1.1.6/tests/gpg' -----BEGIN PGP MESSAGE----- Version: GnuPG v2.0.8 (GNU/Linux) hQEOA2rm1+5GqHH4EAP8CLySAWZ9QFCMUZKwaR80CEXY6WtSerNt30PuO9F3DUE2 FFzLT7rCfTSfa87hpa45dwH2NynxvW/sREFYysARlj3GVFy1jKXHZ2q9sRagCxbP PlpmnXsQ0/tScTJ892HAcB/GeuWPSvJ+Rfo5NpHOpXMQh2qlbvaOV93HFTS5En4D /iJTP7m0/w1+Pgb3SyhIu0sjnFra3pOoGpUe+mCd3KLizOcXcnFE2tZpZCQVmQsU cUDUICjehkj9e8dq7aUkwNi7G0mvspMxyL202i7Z833zvXepjPJlTayNWYMeKIqK EqfELsAqBRQ9vRUcOp29I0NWveeSfckB6nx/zFGSoFoqhQEOA1OB6k7im6N/EAP+ LCjEPPBz5gu8EYtfnwCtUC8SX33aUmFeTpd+kdNGXRC8dsf74A/ZoPciLFWLW63o M3wrz2MQVwHukv6xaSBjnbS4M+nTMtnYzZjXd1OwZZxO048z1Z50IuXFT3QfzMhD K7/YXbn7crXrrnVJ72EHX/nZ2xa0kBGsluZZEgwybmUD/jSgPqcDwydfgCqUDefZ TUMr4BaOyngthQUQcJjzy3x5npGv0SAJx0gkzft8URKBOxaY1zxXxQBIvMVpln0M EznBLzIUh0Xn5ZfjggMAUZyoeIh6iYLizeAVdLPdgwMnlctVjoG/cUb2ZQL24Z4N AJZm6m9S2/N+fuHCRUkf+QLq0kcByRxIm8iWRdBCatPX9ddRvdaBJ7owzxri5J/7 JzGoNoXfsM23sLwumu7sml/DYUV7cy5T78U/uTc14tv5CBXq4fraTcos3w== =bsZL -----END PGP MESSAGE----- PASS: t-encrypt