saymrwulf/cryptography
1
0
Fork 0
mirror of https://github.com/saymrwulf/cryptography.git synced 2026-05-14 20:37:55 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions

re-add the why of cryptography to the faq with some small updates (#3621)

Browse source 
* re-add the why of cryptography to the faq with some small updates

* reorder the items a bit
This commit is contained in:
Paul Kehrer 2017-05-27 14:24:28 -05:00 committed by Alex Gaynor
parent 2f29224beb
commit f916dfcdbc
1 changed files with 19 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

19
docs/faq.rst
View file

@ -14,6 +14,25 @@ to NaCl.
If you prefer NaCl's design, we highly recommend `PyNaCl`_.
Why use ``cryptography``?
-------------------------
If you've done cryptographic work in Python before you have likely encountered
other libraries in Python such as *M2Crypto*, *PyCrypto*, or *PyOpenSSL*. In
building ``cryptography`` we wanted to address a few issues we observed in the
legacy libraries:
* Extremely error prone APIs and insecure defaults.
* Use of poor implementations of algorithms (i.e. ones with known side-channel
attacks).
* Lack of maintenance.
* Lack of high level APIs.
* Lack of PyPy and Python 3 support.
* Poor introspectability and thus poor testability.
* Absence of algorithms such as
:class:`AES-GCM <cryptography.hazmat.primitives.ciphers.modes.GCM>` and
:class:`~cryptography.hazmat.primitives.kdf.hkdf.HKDF`.
Compiling ``cryptography`` on macOS produces a ``fatal error: 'openssl/aes.h' file not found`` error
----------------------------------------------------------------------------------------------------