diff --git a/README b/README index 033d187..9c66e19 100644 --- a/README +++ b/README @@ -1,27 +1,27 @@ DESCRIPTION Pretty Curved Privacy (pcp1) is a commandline utility which can be used - to encrypt files. pcp1 uses eliptc curve cryptography for encryption - (CURVE25519 by Dan J. Bernstein). While CURVE25519 is no worldwide + to encrypt files. pcp1 uses elliptic curve cryptography for encryption + (CURVE25519 by Dan J. Bernstein). While CURVE25519 is not a worldwide accepted standard it hasn't been compromised by the NSA - which might be better, depending on your point of view. - Caution: since CURVE25519 is no accepted standard, pcp1 has to be - considered as experimental software. In fact, I wrote it just to learn + Caution: since CURVE25519 is not an accepted standard, pcp1 has to be + considered experimental software. In fact, I wrote it just to learn about the curve and see how it works. Beside some differences it works like GNUPG. So, if you already know how - to use gpg, you'll feel almost home. + to use gpg, you'll feel almost at home. QUICKSTART Lets say, Alicia and Bobby want to exchange encrypted messages. Here's - what the've got to do. + what they need to do. - First, both have create a secret key: + First, both have to create a secret key: Alicia Bobby pcp1 -k pcp1 -k - After entering their name, email address and a passphrase to protect the + 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, which has to be @@ -32,18 +32,18 @@ QUICKSTART Alicia Bobby 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 + They've got to exchange the public key somehow (which is not my problem at + the moment, use ssh, encrypted mail, etc). Once exchanged, they have to import it: Alicia Bobby pcp1 -K -I bobby.pub pcp1 -K -I alicia.pub - They will see a response as this when done: + They will see a response when this is done: key 0x29A323A2C295D391 added to .pcpvault. - Now, Alicia finally writes the secret message, encrypts it and sends it + Now, Alicia finally writes the secret message, encrypts it, and sends it to Bobby, who in turn decrypts it: Alicia Bobby @@ -84,7 +84,7 @@ FILES AND PIPES ssh remote cat file | pcp1 -ez | mailx -s 'as requested' bob@somewhere - here we encrypt a file symmetrically without downloading it from a + Here we encrypt a file symmetrically without downloading it from a remote ssh server and sending the encrypted result via email to someone. The behavior is the same with any other functionality where files are @@ -151,7 +151,7 @@ ADDITIONAL COPYRIGHTS Random art image from OpenSSH keygen Copyright (c) 2000, 2001 Markus Friedl. All rights reserved. - Comitted by Alexander von Gernler in rev 1.7. + Committed by Alexander von Gernler in rev 1.7. Every incorporated source code is opensource and licensed under the GPL as well. diff --git a/README.pod b/README.pod index 6187207..af9868c 100644 --- a/README.pod +++ b/README.pod @@ -13,22 +13,22 @@ =head1 DESCRIPTION B (pcp1) is a commandline utility which can -be used to encrypt files. B uses eliptc curve cryptography +be used to encrypt files. B uses elliptic curve cryptography for encryption (CURVE25519 by Dan J. Bernstein). While CURVE25519 -is no worldwide accepted standard it hasn't been compromised by +is not a worldwide accepted standard it hasn't been compromised by the NSA - which might be better, depending on your point of view. -B: since CURVE25519 is no accepted standard, B has -to be considered as experimental software. In fact, I wrote it just +B: since CURVE25519 is not an accepted standard, B has +to be considered experimental software. In fact, I wrote it just to learn about the curve and see how it works. Beside some differences it works like B. So, if you already -know how to use gpg, you'll feel almost home. +know how to use gpg, you'll feel almost at home. =head1 QUICKSTART Lets say, Alicia and Bobby want to exchange encrypted messages. -Here's what the've got to do. +Here's what they need to do. First, both have create a secret key: @@ -46,8 +46,8 @@ a derived public key especially for the recipient: Alicia Bobby 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've got to exchange the public key somehow (which is not my +problem at the moment, use ssh, encrypted mail, etc). Once exchanged, they have to import it: Alicia Bobby @@ -57,7 +57,7 @@ They will see a response as this when done: key 0x29A323A2C295D391 added to .pcpvault. -Now, Alicia finally writes the secret message, encrypts it and +Now, Alicia finally writes the secret message, encrypts it, and sends it to Bobby, who in turn decrypts it: Alicia Bobby @@ -100,7 +100,7 @@ realistic example: ssh remote cat file | pcp1 -ez | mailx -s 'as requested' bob@somewhere -here we encrypt a file symmetrically without downloading it from a +Here we encrypt a file symmetrically without downloading it from a remote ssh server and sending the encrypted result via email to someone.