exa/codecrypt
1
0
Fork 0
Code Issues Pull requests Actions Packages Projects Releases Wiki Activity

man: add information about new message format

Browse source
This commit is contained in:
Mirek Kratochvil 2013-09-30 12:15:27 +02:00
parent 5b77413a7f
commit ce43548d32
1 changed files with 8 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

8
man/ccr.1
View file

@ -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 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. 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 .SH EXAMPLE
Following commands roughly demonstrate command line usage of \fBccr\fR: Following commands roughly demonstrate command line usage of \fBccr\fR:
.nf .nf