aboutsummaryrefslogtreecommitdiffstats
path: root/docs/hazmat/primitives/asymmetric/rsa.rst
diff options
context:
space:
mode:
authorPaul Kehrer <paul.l.kehrer@gmail.com>2015-10-12 11:00:30 -0500
committerPaul Kehrer <paul.l.kehrer@gmail.com>2015-10-12 11:00:30 -0500
commit06f360feedb740aa0b4db7683d02accd14bc1732 (patch)
tree06a52f7de217216dc2e0f797f92da9160d9fbc8f /docs/hazmat/primitives/asymmetric/rsa.rst
parent0eafd9cd32a69909bd7bab955459925f54bd7278 (diff)
downloadcryptography-06f360feedb740aa0b4db7683d02accd14bc1732.tar.gz
cryptography-06f360feedb740aa0b4db7683d02accd14bc1732.tar.bz2
cryptography-06f360feedb740aa0b4db7683d02accd14bc1732.zip
add some links to public key loading in the RSA/DSA verification sections
Diffstat (limited to 'docs/hazmat/primitives/asymmetric/rsa.rst')
-rw-r--r--docs/hazmat/primitives/asymmetric/rsa.rst10
1 files changed, 7 insertions, 3 deletions
diff --git a/docs/hazmat/primitives/asymmetric/rsa.rst b/docs/hazmat/primitives/asymmetric/rsa.rst
index f88750cf..de8b2fd0 100644
--- a/docs/hazmat/primitives/asymmetric/rsa.rst
+++ b/docs/hazmat/primitives/asymmetric/rsa.rst
@@ -163,9 +163,13 @@ Verification
~~~~~~~~~~~~
The previous section describes what to do if you have a private key and want to
-sign something. If you have a public key, a message, and a signature, you can
-check that the public key genuinely was used to sign that specific message. You
-also need to know which signing algorithm was used:
+sign something. If you have a public key, a message, a signature, and the
+signing algorithm that was used you can check that the private key associated
+with a given public key was used to sign that specific message. You can obtain
+a public key to use in verification using
+:func:`~cryptography.hazmat.primitives.serialization.load_pem_public_key`,
+:func:`~cryptography.hazmat.primitives.serialization.load_der_public_key`, or
+:meth:`~cryptography.hazmat.primitives.asymmetric.rsa.RSAPrivateKey.public_key`.
.. doctest::