aboutsummaryrefslogtreecommitdiffstats
path: root/docs/glossary.rst
diff options
context:
space:
mode:
authorPaul Kehrer <paul.l.kehrer@gmail.com>2014-03-08 11:09:49 -0400
committerPaul Kehrer <paul.l.kehrer@gmail.com>2014-03-08 11:09:49 -0400
commitbf2a9d9545f39ad0dd9b9c9c4aa2f7f2b5669f0f (patch)
tree083cc465c6fabdb61ff69aadc33b31e8617f2136 /docs/glossary.rst
parentdee5c25d35c53885698bca42015c9f7bbfb27baa (diff)
parent78c2f2d2c0a40d20edcaf37c33e91224af3ecbb6 (diff)
downloadcryptography-bf2a9d9545f39ad0dd9b9c9c4aa2f7f2b5669f0f.tar.gz
cryptography-bf2a9d9545f39ad0dd9b9c9c4aa2f7f2b5669f0f.tar.bz2
cryptography-bf2a9d9545f39ad0dd9b9c9c4aa2f7f2b5669f0f.zip
Merge branch 'master' into idea-bespoke-vectors
* master: (246 commits) Fixed python3 incompatibility Removed dependency on setuptools for version check don't need to move these definitions conditional NIDs for 0.9.8e x509 changes for 0.9.8e support more changes for 0.9.8e support, this time in the ssl.h headers macro switches in evp for 0.9.8e bind some error constants conditionally for 0.9.8e support BIO macro switch for 0.9.8e support move some nids conditionally bind AES_wrap/unwrap for 0.9.8e support Add GPG key fingerprint for lvh change comparison to be easier to read ridiculous workaround time whoops Missing imports Convert stuff Add binding for DSA_new Fix drop in coverage levels by removing branches Added check to turn of CC backend for OS X version < 10.8 ... Conflicts: docs/development/test-vectors.rst
Diffstat (limited to 'docs/glossary.rst')
-rw-r--r--docs/glossary.rst22
1 files changed, 21 insertions, 1 deletions
diff --git a/docs/glossary.rst b/docs/glossary.rst
index 4421fca3..ef422a6e 100644
--- a/docs/glossary.rst
+++ b/docs/glossary.rst
@@ -26,9 +26,29 @@ Glossary
Cryptographic operations where encryption and decryption use the same
key.
+ public-key cryptography
asymmetric cryptography
Cryptographic operations where encryption and decryption use different
- keys. There are separate encryption and decryption keys.
+ keys. There are separate encryption and decryption keys. Typically
+ encryption is performed using a :term:`public key`, and it can then be
+ decrypted using a :term:`private key`. Asymmetric cryptography can also
+ be used to create signatures, which can be generated with a
+ :term:`private key` and verified with a :term:`public key`.
+
+ public key
+ This is one of two keys involved in :term:`public-key cryptography`. It
+ can be used to encrypt messages for someone possessing the
+ corresponding :term:`private key` and to verify signatures created with
+ the corresponding :term:`private key`. This can be distributed
+ publicly, hence the name.
+
+ private key
+ This is one of two keys involved in :term:`public-key cryptography`. It
+ can be used to decrypt messages which were encrypted with the
+ corresponding :term:`public key`, as well as to create signatures,
+ which can be verified with the corresponding :term:`public key`. These
+ **must** be kept secret, if they are exposed, all encrypted messages
+ are compromised, and an attacker will be able to forge signatures.
authentication
The process of verifying that a message was created by a specific