upgrade docs after algo names changed
This commit is contained in:
parent
b5ae7ca4dd
commit
d8a284fe4a
|
@ -26,7 +26,7 @@ Everything is meant to work mostly like GnuPG, but with some good simplicity
|
||||||
margin. Let's play with random data!
|
margin. Let's play with random data!
|
||||||
|
|
||||||
ccr -g help
|
ccr -g help
|
||||||
ccr -g fmtseq128 --name "John Doe" # your signature key
|
ccr -g fmtseq128-sha --name "John Doe" # your signature key
|
||||||
ccr -g mceqd128 --name "John Doe" # your encryption key
|
ccr -g mceqd128 --name "John Doe" # your encryption key
|
||||||
|
|
||||||
ccr -K #watch the generated keys
|
ccr -K #watch the generated keys
|
||||||
|
|
|
@ -274,7 +274,7 @@ Following commands roughly demonstrate command line usage of \fBccr\fR:
|
||||||
.nf
|
.nf
|
||||||
.sp
|
.sp
|
||||||
ccr -g help
|
ccr -g help
|
||||||
ccr -g fmtseq128 --name "John Doe" # your signature key
|
ccr -g fmtseq128-sha --name "John Doe" # your signature key
|
||||||
ccr -g mceqd128 --name "John Doe" # your encryption key
|
ccr -g mceqd128 --name "John Doe" # your encryption key
|
||||||
|
|
||||||
ccr -K #watch the generated keys
|
ccr -K #watch the generated keys
|
||||||
|
|
Loading…
Reference in a new issue