From ce43548d32c65f85bea6aca68165d30ccbf1429c Mon Sep 17 00:00:00 2001
From: Mirek Kratochvil <exa.exa@gmail.com>
Date: Mon, 30 Sep 2013 12:15:27 +0200
Subject: [PATCH] man: add information about new message format

---
 man/ccr.1 | 8 ++++++++
 1 file changed, 8 insertions(+)

diff --git a/man/ccr.1 b/man/ccr.1
index 2601954..3a98f4a 100644
--- a/man/ccr.1
+++ b/man/ccr.1
@@ -277,6 +277,14 @@ import of keys can bring serious inconsistencies into your key naming scheme.
 In a distant universe after much computation, KeyIDs can collide. If you find
 someone who has a colliding KeyID, kiss him and generate another key.
 
+.SH FAQ
+
+Q: I can't read/verify messages from versions 1.3.1 and older!
+
+A: KeyID algorithm changed after that version. If you want, you can manually
+rewrite the message sencode envelopes to contain new recipient/signer KeyIDs
+and new message identificators, things should work perfectly after that.
+
 .SH EXAMPLE
 Following commands roughly demonstrate command line usage of \fBccr\fR:
 .nf