gnupg/NEWS

42 lines
1.8 KiB
Plaintext
Raw Normal View History

1998-01-12 11:18:17 +01:00
1998-02-04 19:54:31 +01:00
* It's now 64 bit clean and runs fine on an alpha--linux.
* Key generation is much faster now. I fixed this by using not
so strong random number for the primes (this was a bug because the
ElGamal primes are public parameters and it does not make sense
to generate them from strong random). The real secret is the x value
which is still generated from strong (okay: /dev/random) random bits.
1998-01-30 17:23:16 +01:00
1998-02-04 19:54:31 +01:00
* added option "--status-fd": see g10/OPTIONS
1998-01-30 17:23:16 +01:00
1998-01-28 17:09:43 +01:00
* We have secure memeory on systems which support mlock().
It is not complete yet, because we do not have signal handler
which does a cleanup in very case.
We should also check the ulimit for the user in the case
that the admin does not have set a limit on locked pages.
* started with internationalization support.
1998-01-25 19:56:33 +01:00
* The logic to handle the web of trust is now implemented. It is
has some bugs; but I'm going to change the algorithm anyway.
It works by calculating the trustlevel on the fly. It may ask
you to provide trust parameters if the calculated trust probability
is too low. I will write a paper which discusses this new approach.
* a couple of changes to the configure script.
1998-01-16 22:15:24 +01:00
* New option "--quick-random" which uses a much quicker random
number generator. Keys generated while this option is in effect
are flags with "INSECURE!" in the user-id. This is a development
only option.
* Read support for new version packets (OpenPGP).
1998-01-28 17:09:43 +01:00
* Comment packets are now of correct OpenPGP type 16. Old comment
packets written by G10 are detected because they always start with
1998-01-16 22:15:24 +01:00
a hash which is an invalid version byte.
1998-01-12 11:18:17 +01:00
* The string "(INSECURE!)" is appended to a new user-id if this
is generated on a system without a good random number generator.