Hello everybody,
I have a simple question. I've been reading the "Random Numbers" chapter
from the Libgcrypt Reference Manual and I haven't seen a way to manually
establishing the seed of the CSPRNG algorithms (may be because that
could make a CSPRNG produce not Cryptographically Secure random
seq
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
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
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 2
n date.
Am I missing anything?. I am using GPG 1.4.10. I would consider moving
to GPG 2 if necessary.
PS: We could manage with revocation signatures, but people would need to
refresh the keys. With a expired signatures people would need to refresh
to see the extension, so they would do.
- --
Jesu
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 14/04/11 06:05, Daniel Kahn Gillmor wrote:
> On 04/13/2011 10:43 PM, Jesus Cea wrote:
>> My idea was to create a signature with a expiration date, so signatures
>> should be renewed every year. The OpenPGP Standard documents
