security-and-privacy/gnupg
security-and-privacy/gnupg
1
0
Fork 0
mirror of git://git.gnupg.org/gnupg.git synced 2024-12-23 10:29:58 +01:00
Code Activity

cipher deprecated warning explained

Browse Source
This commit is contained in:
Nils Ellmenreich 2000-12-19 15:39:57 +00:00
parent 04beb81571
commit d188c1c37f
2 changed files with 23 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

17
doc/FAQ
View File

@ -2,8 +2,8 @@
GNUPG FREQUENTLY ASKED QUESTIONS
Version: 0.35
Last-Modified: Dec 14, 2000
Version: 0.36
Last-Modified: Dec 19, 2000
Maintained-by: Nils Ellmenreich <nils 'at' gnupg.org>
@ -83,7 +83,8 @@ you could search in the mailing list archive.
6.10) If I submit a key to a keyserver, nothing happens ...
6.11) I get "gpg: waiting for lock ..."
6.12) Older gpg's (e.g., 1.0) have problems with keys from newer gpgs ...
6.13) I still have a problem. How do I report a bug?
6.13) With 1.0.4, I get "this cipher algorithm is deprecated ..."
6.14) I still have a problem. How do I report a bug?
7. ADVANCED TOPICS
7.1) How does this whole thing work?
@ -638,7 +639,15 @@ in it - why?
force gpg to use a previous default cipher algo by putting
cipher-algo cast5 into your options file.
6.13) I still have a problem. How do I report a bug?
6.13) With 1.0.4, I get "this cipher algorithm is deprecated ..."
If you just generated a new key and get this message while
encrypting, you've witnessed a bug in 1.0.4. It uses the new AES
cipher Rijndael that is incorrectly being referred as
"deprecated". Ignore this warning, more recent versions of gpg are
corrected.
6.14) I still have a problem. How do I report a bug?
Are you sure that it's not been mentioned somewhere on the mailing
lists? Did you have a look at the bug list (You'll find a link to

12
doc/faq.raw
View File

@ -13,8 +13,8 @@ The most recent version of the FAQ is available from
[H H1]GNUPG FREQUENTLY ASKED QUESTIONS[H /H1]
Version: 0.35[H p]
Last-Modified: Dec 14, 2000[H p]
Version: 0.36[H p]
Last-Modified: Dec 19, 2000[H p]
Maintained-by: [$maintainer]
@ -607,6 +607,14 @@ in it - why?
force gpg to use a previous default cipher algo by putting
[H pre]cipher-algo cast5[H /pre] into your options file.
<Q> With 1.0.4, I get "this cipher algorithm is deprecated ..."
If you just generated a new key and get this message while
encrypting, you've witnessed a bug in 1.0.4. It uses the new AES
cipher Rijndael that is incorrectly being referred as
"deprecated". Ignore this warning, more recent versions of gpg are
corrected.
<Q> I still have a problem. How do I report a bug?
Are you sure that it's not been mentioned somewhere on the mailing