Compiling GnuPG for Windows

2014-06-23 Thread Dr. Vesselin Bontchev
Thank you, guys, for your input. Apparently, GnuPG is not suitable for use in my environment. (And not just because I am unable to compile it on my machine. Bugs, annoyances, wrong documentation, incompatibilities...) I already wasted three weeks trying to make it work according to my needs and

Re: Broken ECDSA in gnupg 2.0.23

2014-06-23 Thread Werner Koch
On Sat, 21 Jun 2014 15:14, anatol.pomo...@gmail.com said: > The libgcrypt functions such as gcry_pk_map_name() return GCRY_PK_ECC > instead of GCRY_PK_ECDSA. So I modified gnupg 2.0.23 sources with this > patch: Thanks. Applied. Shalom-Salam, Werner -- Die Gedanken sind frei. Ausnahmen

Re: mascot_p

2014-06-23 Thread MichaelQuigley
> - Message from MFPA <2014-667rhzu3dc-lists-gro...@riseup.net> on > > > Some animal that hides > > stuff? > > A squirrel? > > > > > Or just a nice animal, > > OK, that rules out a squirrel: it is essentially a rat with good PR. > (-; > Perhaps it's just PR, but they seem to live

[Announce] [security fix] GnuPG 1.4.17 released

2014-06-23 Thread Werner Koch
Hello! We are pleased to announce the availability of a new stable GnuPG-1 release: Version 1.4.17. This release includes a *security fix* to stop a possible DoS using garbled compressed data packets which can be used to put gpg into an infinite loop. The GNU Privacy Guard (GnuPG) is GNU's tool

Re: [Announce] [security fix] GnuPG 1.4.17 released

2014-06-23 Thread Kristian Fiskerstrand
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 06/23/2014 06:21 PM, Werner Koch wrote: > Hello! > Hi > > * Avoid DoS due to garbled compressed data packets. Is this CVE-2013-4402 as fixed in 2.0.22 or a new bug? - -- - Kristian Fiskerstrand Blog: http://bl

Re: [Announce] [security fix] GnuPG 1.4.17 released

2014-06-23 Thread Kristian Fiskerstrand
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 06/23/2014 07:19 PM, Kristian Fiskerstrand wrote: > On 06/23/2014 06:21 PM, Werner Koch wrote: >> Hello! > > > Hi > > >> * Avoid DoS due to garbled compressed data packets. > > > Is this CVE-2013-4402 as fixed in 2.0.22 or a new bug? > Nev

Re: Compiling GnuPG for Windows

2014-06-23 Thread Robert J. Hansen
> Apparently, GnuPG is not suitable for use in my environment. (And not > just because I am unable to compile it on my machine. Bugs, > annoyances, wrong documentation, incompatibilities...) We would appreciate it if you would list the bugs, annoyances, documentation errors, and incompatibilities

Re: [Announce] [security fix] GnuPG 1.4.17 released

2014-06-23 Thread Charly Avital
Hi, Version info: gnupg 1.4.17 Configured for: Darwin (x86_64-apple-darwin13.2.0) Thanks, Charly 0x15E4F2EA OS X OS X 10.9.3 (13D65) gpg (GnuPG) 1.4.17 TB 24.6.0 Enigmail version 1.7.a1pre 2014/04/06 ___ Gnupg-users mailing list Gnupg-users@gnupg.

Re: Compiling GnuPG for Windows

2014-06-23 Thread Doug Barton
On 6/23/2014 1:26 AM, Dr. Vesselin Bontchev wrote: Thank you, guys, for your input. Apparently, GnuPG is not suitable for use in my environment. (And not just because I am unable to compile it on my machine. Out of curiosity, why do you believe that you need to compile it? Doug ___

riseup.net OpenPGP Best Practices article

2014-06-23 Thread Fraser Tweedale
Hi all, An OpenPGP Best Practices article from riseup.net has been doing the rounds today. Quite a lot of good info, especially regarding key strength and expiry, and digest preferences. https://help.riseup.net/en/gpg-best-practices Cheers, Fraser _

GnuPG 2.1.0-beta442: t-timestuff.c:118: test 17 failed

2014-06-23 Thread Claus Assmann
On OpenBSD 5.3 i386 one test fails: t-timestuff.c:118: test 17 failed FAIL: t-timestuff This patch (hack?) fixes it for me (local timezone is PDT). --- t-timestuff.c- Mon Jun 23 19:33:25 2014 +++ t-timestuff.c Mon Jun 23 19:33:38 2014 @@ -146,6 +146,7 @@ (void)argc; (void)argv;

Re: riseup.net OpenPGP Best Practices article

2014-06-23 Thread Werner Koch
On Tue, 24 Jun 2014 05:55, fr...@frase.id.au said: > rounds today. Quite a lot of good info, especially regarding key > strength and expiry, and digest preferences. Just for the records: _I_ do not consider the use of a 4096 bit RSA key and a preference for SHA-512 a best practice. For a secure