updated manpage+readme

README.pod

@@ -26,10 +26,13 @@ First, both have create a secret key:
 After entering their name, email address and a passphrase to protect
 the key, it will be stored in their B<vault file> (by default ~/.pcpvault).
 
-Now, both of them have to export the public key part of their key:
+Now, both of them have to export the public key, which has to be
+imported by the other one. With B<pcp> you can export the public
+part of your primary key, but the better solution is to export
+a derived public key especially for the recipient:
 
  Alicia                             Bobby
- pcp1 -p -O alicia.pub              pcp1 -p -O bobby.pub
+ pcp1 -p -r Bobby -O alicia.pub     pcp1 -p -r Alicia -O bobby.pub
 
 They've to exchange the public key somehow (which is not my
 problem at the moment, use ssh, encrypted mail, whatever). Once exchanged,

README.txt

@@ -24,10 +24,13 @@ QUICKSTART
     After entering their name, email address and a passphrase to protect the
     key, it will be stored in their vault file (by default ~/.pcpvault).
 
-    Now, both of them have to export the public key part of their key:
+    Now, both of them have to export the public key, which has to be
+    imported by the other one. With pcp you can export the public part of
+    your primary key, but the better solution is to export a derived public
+    key especially for the recipient:
 
      Alicia                             Bobby
-     pcp1 -p -O alicia.pub              pcp1 -p -O bobby.pub
+     pcp1 -p -r Bobby -O alicia.pub     pcp1 -p -r Alicia -O bobby.pub
 
     They've to exchange the public key somehow (which is not my problem at
     the moment, use ssh, encrypted mail, whatever). Once exchanged, they

man/Makefile.in

@@ -1,4 +1,4 @@
-# Makefile.in generated by automake 1.12.6 from Makefile.am.
+# Makefile.in generated by automake 1.12.4 from Makefile.am.
 # @configure_input@
 
 # Copyright (C) 1994-2012 Free Software Foundation, Inc.

man/details.pod

@@ -28,6 +28,20 @@ this writing I'm not sure if this was a good idea>).
 If you just want to know details about a key or the vault, use the
 B<-t> option.
 
+=head2 Derived Public Keys
+
+In the real world you would not use your primary key to encrypt
+messages, because this would require to send the public key part
+to your recipient in one way or another. The much better and more
+secure way is to use a B<Derived Public Key>:
+
+Such a key will be dynamically generated from a hash of your
+primary secret key and the recipient (an email address, name or key id).
+The public part of this dynamic key will be exported and sent to
+the recipient. A public key generated this way will only be usable
+by the recipient (and yourself) and each recipient will have a different
+public key from you (and vice versa).
+
 =head1 INTERNALS
 
 FIXME.

man/pcp.pod

@@ -26,10 +26,13 @@ First, both have create a secret key:
 After entering their name, email address and a passphrase to protect
 the key, it will be stored in their B<vault file> (by default ~/.pcpvault).
 
-Now, both of them have to export the public key part of their key:
+Now, both of them have to export the public key, which has to be
+imported by the other one. With B<pcp> you can export the public
+part of your primary key, but the better solution is to export
+a derived public key especially for the recipient:
 
  Alicia                             Bobby
- pcp1 -p -O alicia.pub              pcp1 -p -O bobby.pub
+ pcp1 -p -r Bobby -O alicia.pub     pcp1 -p -r Alicia -O bobby.pub
 
 They've to exchange the public key somehow (which is not my
 problem at the moment, use ssh, encrypted mail, whatever). Once exchanged,

man/pcp1.1

@@ -1,4 +1,4 @@
-.\" Automatically generated by Pod::Man 2.25 (Pod::Simple 3.16)
+.\" Automatically generated by Pod::Man 2.23 (Pod::Simple 3.14)
 .\"
 .\" Standard preamble:
 .\" ========================================================================
@@ -233,11 +233,14 @@ First, both have create a secret key:
 After entering their name, email address and a passphrase to protect
 the key, it will be stored in their \fBvault file\fR (by default ~/.pcpvault).
 .PP
-Now, both of them have to export the public key part of their key:
+Now, both of them have to export the public key, which has to be
+imported by the other one. With \fBpcp\fR you can export the public
+part of your primary key, but the better solution is to export
+a derived public key especially for the recipient:
 .PP
 .Vb 2
 \& Alicia                             Bobby
-\& pcp1 \-p \-O alicia.pub              pcp1 \-p \-O bobby.pub
+\& pcp1 \-p \-r Bobby \-O alicia.pub     pcp1 \-p \-r Alicia \-O bobby.pub
 .Ve
 .PP
 They've to exchange the public key somehow (which is not my
@@ -309,6 +312,19 @@ this writing I'm not sure if this was a good idea\fR).
 .PP
 If you just want to know details about a key or the vault, use the
 \&\fB\-t\fR option.
+.SS "Derived Public Keys"
+.IX Subsection "Derived Public Keys"
+In the real world you would not use your primary key to encrypt
+messages, because this would require to send the public key part
+to your recipient in one way or another. The much better and more
+secure way is to use a \fBDerived Public Key\fR:
+.PP
+Such a key will be dynamically generated from a hash of your
+primary secret key and the recipient (an email address, name or key id).
+The public part of this dynamic key will be exported and sent to
+the recipient. A public key generated this way will only be usable
+by the recipient (and yourself) and each recipient will have a different
+public key from you (and vice versa).
 .SH "INTERNALS"
 .IX Header "INTERNALS"
 \&\s-1FIXME\s0.

man/pcp1.pod

@@ -105,10 +105,13 @@ First, both have create a secret key:
 After entering their name, email address and a passphrase to protect
 the key, it will be stored in their B<vault file> (by default ~/.pcpvault).
 
-Now, both of them have to export the public key part of their key:
+Now, both of them have to export the public key, which has to be
+imported by the other one. With B<pcp> you can export the public
+part of your primary key, but the better solution is to export
+a derived public key especially for the recipient:
 
  Alicia                             Bobby
- pcp1 -p -O alicia.pub              pcp1 -p -O bobby.pub
+ pcp1 -p -r Bobby -O alicia.pub     pcp1 -p -r Alicia -O bobby.pub
 
 They've to exchange the public key somehow (which is not my
 problem at the moment, use ssh, encrypted mail, whatever). Once exchanged,
@@ -175,6 +178,20 @@ this writing I'm not sure if this was a good idea>).
 If you just want to know details about a key or the vault, use the
 B<-t> option.
 
+=head2 Derived Public Keys
+
+In the real world you would not use your primary key to encrypt
+messages, because this would require to send the public key part
+to your recipient in one way or another. The much better and more
+secure way is to use a B<Derived Public Key>:
+
+Such a key will be dynamically generated from a hash of your
+primary secret key and the recipient (an email address, name or key id).
+The public part of this dynamic key will be exported and sent to
+the recipient. A public key generated this way will only be usable
+by the recipient (and yourself) and each recipient will have a different
+public key from you (and vice versa).
+
 =head1 INTERNALS
 
 FIXME.