aboutsummaryrefslogtreecommitdiffstats
path: root/docs/x509
diff options
context:
space:
mode:
authorAlex Gaynor <alex.gaynor@gmail.com>2016-03-14 12:34:52 -0400
committerAlex Gaynor <alex.gaynor@gmail.com>2016-03-14 12:34:52 -0400
commit1cc38905dae926378f7b98d96ff668dfaa0eb3d5 (patch)
treee6899436c40392b9319f2108e3747c3c0c0a51d8 /docs/x509
parent84c58c45f250f777ac00536f1932292669ce0811 (diff)
downloadcryptography-1cc38905dae926378f7b98d96ff668dfaa0eb3d5.tar.gz
cryptography-1cc38905dae926378f7b98d96ff668dfaa0eb3d5.tar.bz2
cryptography-1cc38905dae926378f7b98d96ff668dfaa0eb3d5.zip
rephrase
Diffstat (limited to 'docs/x509')
-rw-r--r--docs/x509/tutorial.rst3
1 files changed, 2 insertions, 1 deletions
diff --git a/docs/x509/tutorial.rst b/docs/x509/tutorial.rst
index ecdd4c1e..6941372f 100644
--- a/docs/x509/tutorial.rst
+++ b/docs/x509/tutorial.rst
@@ -89,7 +89,8 @@ Creating a self-signed certificate
While most of the time you want a certificate that has been *signed* by someone
else (i.e. a certificate authority), so that trust is established, sometimes
you want to create a self-signed certificate. Self-signed certificates are not
-issued by a certificate authority, but are instead signed by themselves.
+issued by a certificate authority, but instead they are signed by the private
+key corresponding to the public key they embed.
This means that other people don't trust these certificates, but it also means
they can be issued very easily. In general the only use case for a self-signed