cryptography is a package designed to expose cryptographic primitives and recipes to Python developers.
Find a file
2020-06-12 08:50:55 -05:00
.github fixed new flake8 error (#5248) 2020-05-12 20:06:06 -05:00
.travis pin certbot deps (#5264) 2020-06-01 15:19:51 -05:00
docs Clarify that static linkage only applies to wheels (#5265) 2020-06-03 11:15:28 -05:00
src Consistently use 'self' in backend.py (#5261) 2020-05-27 08:31:51 -04:00
tests Cleanup serialize (#5149) 2020-05-25 13:17:25 -05:00
vectors Test vectors for OpenSSH serialization format (#5151) 2020-05-25 13:24:17 -05:00
.coveragerc properly merge pypy coverage with coveragerc paths 2016-01-07 10:41:04 -08:00
.gitattributes test py27 with windows container on azure (#4880) 2019-05-08 18:29:42 -04:00
.gitignore Add bindings for SSL_OP_NO_DTLS* (#4079) 2018-01-16 09:07:23 -06:00
.travis.yml Test on LibreSSL 3.2.0 (#5263) 2020-06-01 17:08:49 -05:00
AUTHORS.rst Add RFC 4514 Distinguished Name formatting for Name, RDN and NameAttribute (#4304) 2018-12-08 09:26:07 +08:00
CHANGELOG.rst Deprecate support for Python 2 (#5251) 2020-05-16 21:58:30 -05:00
codecov.yml revert codecov.yml workaround and pin coverage to 4.3.4 (#3662) 2017-06-03 14:26:56 -04:00
CONTRIBUTING.rst link the CONTRIBUTING.rst to the development section of our docs 2014-03-02 09:23:46 -04:00
dev-requirements.txt goodbye azure (#5207) 2020-04-19 20:32:28 -04:00
LICENSE nit in LICENSE, itself doesn't make sense here (#4016) 2017-11-10 08:29:14 +08:00
LICENSE.APACHE HTTPS a bunch of links in random places (#4666) 2018-12-31 10:10:09 -06:00
LICENSE.BSD Added new license files. Refs #1209 2014-10-31 07:51:41 -07:00
LICENSE.PSF C locking callback (#3226) 2016-11-13 12:55:22 -08:00
MANIFEST.in goodbye azure (#5207) 2020-04-19 20:32:28 -04:00
pyproject.toml Comply with PEP 508 by using platform_python_implementation (#5006) 2019-10-17 10:32:28 +08:00
README.rst fix CI badge again since naming it breaks the link (#5162) 2020-03-30 22:40:45 -04:00
release.py goodbye azure (#5207) 2020-04-19 20:32:28 -04:00
rtd-requirements.txt install only the minimum required to build our docs for rtd (#4133) 2018-03-05 19:50:10 -05:00
setup.py Block a sphinx version that's broken (#5272) 2020-06-12 08:50:55 -05:00
tox.ini goodbye azure (#5207) 2020-04-19 20:32:28 -04:00

pyca/cryptography
=================

.. image:: https://img.shields.io/pypi/v/cryptography.svg
    :target: https://pypi.org/project/cryptography/
    :alt: Latest Version

.. image:: https://readthedocs.org/projects/cryptography/badge/?version=latest
    :target: https://cryptography.io
    :alt: Latest Docs

.. image:: https://travis-ci.org/pyca/cryptography.svg?branch=master
    :target: https://travis-ci.org/pyca/cryptography

.. image:: https://github.com/pyca/cryptography/workflows/CI/badge.svg?branch=master
    :target: https://github.com/pyca/cryptography/actions?query=workflow%3ACI+branch%3Amaster

.. image:: https://codecov.io/github/pyca/cryptography/coverage.svg?branch=master
    :target: https://codecov.io/github/pyca/cryptography?branch=master


``cryptography`` is a package which provides cryptographic recipes and
primitives to Python developers.  Our goal is for it to be your "cryptographic
standard library". It supports Python 2.7, Python 3.5+, and PyPy 5.4+.

``cryptography`` includes both high level recipes and low level interfaces to
common cryptographic algorithms such as symmetric ciphers, message digests, and
key derivation functions. For example, to encrypt something with
``cryptography``'s high level symmetric encryption recipe:

.. code-block:: pycon

    >>> from cryptography.fernet import Fernet
    >>> # Put this somewhere safe!
    >>> key = Fernet.generate_key()
    >>> f = Fernet(key)
    >>> token = f.encrypt(b"A really secret message. Not for prying eyes.")
    >>> token
    '...'
    >>> f.decrypt(token)
    'A really secret message. Not for prying eyes.'

You can find more information in the `documentation`_.

You can install ``cryptography`` with:

.. code-block:: console

    $ pip install cryptography

For full details see `the installation documentation`_.

Discussion
~~~~~~~~~~

If you run into bugs, you can file them in our `issue tracker`_.

We maintain a `cryptography-dev`_ mailing list for development discussion.

You can also join ``#cryptography-dev`` on Freenode to ask questions or get
involved.

Security
~~~~~~~~

Need to report a security issue? Please consult our `security reporting`_
documentation.


.. _`documentation`: https://cryptography.io/
.. _`the installation documentation`: https://cryptography.io/en/latest/installation/
.. _`issue tracker`: https://github.com/pyca/cryptography/issues
.. _`cryptography-dev`: https://mail.python.org/mailman/listinfo/cryptography-dev
.. _`security reporting`: https://cryptography.io/en/latest/security/