mirror of
git://git.gnupg.org/gnupg.git
synced 2025-01-21 14:47:03 +01:00
* NEWS: Note that 1.4 won't have Elgamal sign+encrypt support at all.
This commit is contained in:
parent
e9fabace03
commit
4cee9a453a
@ -1,3 +1,8 @@
|
||||
2003-12-21 David Shaw <dshaw@jabberwocky.com>
|
||||
|
||||
* NEWS: Note that 1.4 won't have Elgamal sign+encrypt support at
|
||||
all.
|
||||
|
||||
2003-12-03 Werner Koch <wk@gnupg.org>
|
||||
|
||||
Released 1.2.4rc1.
|
||||
|
9
NEWS
9
NEWS
@ -8,13 +8,16 @@ Noteworthy changes in version 1.2.4 (unreleased)
|
||||
* Added the ability to handle messages that can be decrypted with
|
||||
either a passphrase or a secret key.
|
||||
|
||||
* Support for Elgamal sign+encrypt keys has been removed. Old
|
||||
signatures may still be verified, and existing encrypted
|
||||
* Most support for Elgamal sign+encrypt keys has been removed.
|
||||
Old signatures may still be verified, and existing encrypted
|
||||
messages may still be decrypted, but no new signatures may be
|
||||
issued by, and no new messages will be encrypted to, these keys.
|
||||
Elgamal sign+encrypt keys are not part of the web of trust. The
|
||||
only new message that can be generated by an Elgamal
|
||||
sign+encrypt key is a key revocation.
|
||||
sign+encrypt key is a key revocation. Note that in a future
|
||||
version of GnuPG (currently planned for 1.4), all support for
|
||||
Elgamal sign+encrypt keys will be removed, so take this
|
||||
opportunity to revoke old keys now.
|
||||
|
||||
* A Russian translation is included again as well as a new
|
||||
Belarusian translation.
|
||||
|
Loading…
x
Reference in New Issue
Block a user