Danger
This is a “Hazardous Materials” module. You should ONLY use it if you’re 100% absolutely sure that you know what you’re doing because this module is full of land mines, dragons, and dinosaurs with laser guns.
OpenSSL backend¶
The OpenSSL C library. Cryptography supports version 0.9.8e
(present in
Red Hat Enterprise Linux 5) and greater. Earlier versions may work but are
not tested or supported.
-
cryptography.hazmat.backends.openssl.
backend
¶ This is the exposed API for the OpenSSL backend.
It implements the following interfaces:
CipherBackend
CMACBackend
DERSerializationBackend
DSABackend
EllipticCurveBackend
HashBackend
HMACBackend
PBKDF2HMACBackend
RSABackend
PEMSerializationBackend
X509Backend
It also exposes the following:
-
name
¶ The string name of this backend:
"openssl"
-
activate_osrandom_engine
()¶ Activates the OS random engine. This will effectively disable OpenSSL’s default CSPRNG.
-
activate_builtin_random
()¶ This will activate the default OpenSSL CSPRNG.
OS random engine¶
OpenSSL uses a user-space CSPRNG that is seeded from system random (
/dev/urandom
or CryptGenRandom
). This CSPRNG is not reseeded
automatically when a process calls fork()
. This can result in situations
where two different processes can return similar or identical keys and
compromise the security of the system.
The approach this project has chosen to mitigate this vulnerability is to
include an engine that replaces the OpenSSL default CSPRNG with one that
sources its entropy from /dev/urandom
on UNIX-like operating systems and
uses CryptGenRandom
on Windows. This method of pulling from the system pool
allows us to avoid potential issues with initializing the RNG as well as
protecting us from the fork()
weakness.
This engine is active by default when importing the OpenSSL backend. When active this engine will be used to generate all the random data OpenSSL requests.
When importing only the binding it is added to the engine list but not activated.
OS random sources¶
On OS X and FreeBSD /dev/urandom
is an alias for /dev/random
and
utilizes the Yarrow algorithm.
On Windows the implementation of CryptGenRandom
depends on which version of
the operation system you are using. See the Microsoft documentation for more
details.
Linux uses its own PRNG design. /dev/urandom
is a non-blocking source
seeded from the same pool as /dev/random
.