aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorWerner Koch <[email protected]>2002-04-29 12:25:35 +0000
committerWerner Koch <[email protected]>2002-04-29 12:25:35 +0000
commit1e1198a4509914c17306341e7caa9a33a60c8c1e (patch)
tree926955d3e82f3385795a545eb9138c73afb03585
parent* pl.po: Update. (diff)
downloadgnupg-1e1198a4509914c17306341e7caa9a33a60c8c1e.tar.gz
gnupg-1e1198a4509914c17306341e7caa9a33a60c8c1e.zip
* faq.raw: Inserted Douglas Calvert as new maintainer. Acknowledge
Nils. Add entry about trust packet parsing problems.
-rw-r--r--doc/ChangeLog3
-rw-r--r--doc/faq.raw13
2 files changed, 12 insertions, 4 deletions
diff --git a/doc/ChangeLog b/doc/ChangeLog
index 1b4d11a2f..f218008fe 100644
--- a/doc/ChangeLog
+++ b/doc/ChangeLog
@@ -2,7 +2,8 @@
* samplekeys.asc: Added gnupg distribution key 57548DCD.
- * faq.raw: Inserted Douglas Calvert as new maintainer.
+ * faq.raw: Inserted Douglas Calvert as new maintainer. Acknowledge
+ Nils. Add entry about trust packet parsing problems.
2002-04-24 David Shaw <[email protected]>
diff --git a/doc/faq.raw b/doc/faq.raw
index a1bfa50d9..a444204cd 100644
--- a/doc/faq.raw
+++ b/doc/faq.raw
@@ -717,6 +717,13 @@ in it - why?
configure script and place a [H pre]unset CDPATH[H /pre] statement
below it.
+<Q> Why does GnuPG 1.0.6 bail out on keyrings used with 1.0.7?
+
+ There is a small bug in 1.0.6 which didn't parse trust packets
+ currectly. You may want to apply this patch if you can't upgrade:
+ http://www.gnupg.org/developer/gpg-woody-fix.txt
+
+
<S> ADVANCED TOPICS
@@ -910,9 +917,9 @@ material?
<S> ACKNOWLEDGEMENTS
- Many thanks to Werner Koch for the original FAQ file and to all
- posters to gnupg-users and gnupg-devel. They all provided most of
- the answers.
+ Many thanks to Nils Ellmenreich for maintaining this FAQ file for
+ a long time and to all posters to gnupg-users and gnupg-devel. They
+ all provided most of the answers.
Also thanks to Casper Dik for providing me with a script to generate
this FAQ (he uses it for the excellent Solaris2 FAQ).