Upgraded to 2.0.28. No improvements in this area.
Any hint?.
I am surprised and dissapointed that 1.4.19 does this in 7 seconds and
2.0.27/2.0.28 are taking minutes. I am sure there is something "fishy"
going on.
Please, advice/hints.
On 29/03/15 19:41, Jesus Cea wrote:
> On 28/03/15 11:48, W
On 28/03/15 11:48, Werner Koch wrote:
> On Fri, 27 Mar 2015 17:07, j...@jcea.es said:
>
>> My problem is that any change to the pubring, like downloading a new
>> key, refreshing, adding a new local signature with "--lsign", etc., will
>> force a trustdb update (in the next execution. For instance
On Sat, 28 Mar 2015 19:58, dougb@dougbarton.email said:
> Just out of curiosity, do you have an ETA on a new release?
Nothing really important has changed since mid February except for a fix
in gpgtar - does anyone really use it on non-Windows? (it has been
fixed in gpg4win).
Salam-Shalom,
On 3/28/15 3:48 AM, Werner Koch wrote:
Sorry for this. It has already been fixed in the repo,
Just out of curiosity, do you have an ETA on a new release?
--
I am conducting an experiment in the efficacy of PGP/MIME signatures.
This message should be signed. If it is not, or the signature doe
On Fri, 27 Mar 2015 17:07, j...@jcea.es said:
> My problem is that any change to the pubring, like downloading a new
> key, refreshing, adding a new local signature with "--lsign", etc., will
> force a trustdb update (in the next execution. For instance, decrypting
A new key signature may chnage
I upgraded my GNUPG form 1.4.x to 2.0.27. I kept the configuration,
public and private keyrings. I have recreated the trustdb from scratch,
trying to solve this, with no success (using "--export-ownertrust").
My pubring.gpg is 34MB in size and I usually create local signatures via
--lsign".
My pr
