On Tue, 2 Feb 2021 09:45, Christoph Biedl said:
> IMnsHO it's a bad idea to remove gnupg1 any time soon. While it
> certainly should not be used for encryption, it's still needed when
> dealing with older keys. Quoting the package description: "It is
And first of all with data encrypted to old k
Hi!
the incompatibility with libgnutls26 can be fixed by using the patch
below. We use this in Gpg4win.
(patches/gnutls-2.12.23/fix-gcrypt-private-api-usage.patch)
Salam-Shalom,
Werner
#! /bin/sh
patch -p0 -l -f $* < $0
exit $?
2014-08-06 Andre Heinecke
* lib/gcrypt/init.c: Us
On Wed, 04 May 2005 14:08:05 +, Brian M Carlson said:
> * Update to 1.4.1.
I'd really prefer that. 1.4.1 has been released more than 6 weeks ago
and fixes quite some bugs we figured out in 1.4.0. The case with
1.4.0 was that people don't care anymore about RC releases and start
complaining o
On Wed, 23 Mar 2005 00:40:23 -0800, Steve Langasek said:
> Given that this bug is marked "grave", should gnupg 1.4.0-3 be pushed into
> testing, or is there another fix we should prefer here?
Although I'd prefer to see 1.4.1 in testing, updating to 1.2.7 would
solve this bug.
Shalom-Salam,
On Wed, 14 Apr 2004 12:04:57 +0200, J H M Dassen (Ray) said:
> It's a side effect of our wide use of GnuTLS in order to avoid the issue of
> needing explicit exemption clauses in order to be able to redistribute
> works based on GPLed code that use the OpenSSL library.
I know and this is for sure
On Wed, 14 Apr 2004 09:44:01 +0100, Colin Watson said:
> It is very painful to change the version of libgcrypt7 in base at this
> point. Doing this will break debian-installer testing, which is the
> reason we asked for no further changes to the package lists in the base
I was not aware of the wi
e.
We will release 1.2 this week - it will merely be a changed version
number.
Werner
--
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
7 matches
Mail list logo
