skeuomorf | bc26efb | 2014-01-29 08:31:47 +0200 | [diff] [blame] | 1 | Installing |
| 2 | ========== |
| 3 | |
| 4 | You can install ``cryptography`` with ``pip``: |
| 5 | |
| 6 | .. code-block:: console |
| 7 | |
| 8 | $ pip install cryptography |
| 9 | |
| 10 | Installation Notes |
| 11 | ================== |
| 12 | On Windows |
| 13 | ---------- |
skeuomorf | b0293bf | 2014-01-29 21:41:02 +0200 | [diff] [blame] | 14 | If you're on Windows you'll need to make sure you have OpenSSL installed. |
| 15 | There are `pre-compiled binaries`_ available. If your installation is in |
| 16 | an unusual location set the ``LIB`` and ``INCLUDE`` environment variables |
| 17 | to include the corresponding locations. For example: |
skeuomorf | bc26efb | 2014-01-29 08:31:47 +0200 | [diff] [blame] | 18 | |
skeuomorf | b0293bf | 2014-01-29 21:41:02 +0200 | [diff] [blame] | 19 | .. code-block:: console |
| 20 | |
| 21 | C:\> \path\to\vcvarsall.bat x86_amd64 |
| 22 | C:\> set LIB=C:\OpenSSL-1.0.1f-64bit\lib;%LIB% |
| 23 | C:\> set INCLUDE=C:\OpenSSL-1.0.1f-64bit\include;%INCLUDE% |
| 24 | C:\> pip install cryptography |
skeuomorf | bc26efb | 2014-01-29 08:31:47 +0200 | [diff] [blame] | 25 | |
| 26 | Using your own OpenSSL on Linux |
| 27 | ------------------------------- |
| 28 | |
| 29 | Python links to OpenSSL for its own purposes and this can sometimes cause |
| 30 | problems when you wish to use a different version of OpenSSL with cryptography. |
| 31 | If you want to use cryptography with your own build of OpenSSL you will need to |
| 32 | make sure that the build is configured correctly so that your version of |
| 33 | OpenSSL doesn't conflict with Python's. |
| 34 | |
| 35 | The options you need to add allow the linker to identify every symbol correctly |
| 36 | even when multiple versions of the library are linked into the same program. If |
| 37 | you are using your distribution's source packages these will probably be |
| 38 | patched in for you already, otherwise you'll need to use options something like |
| 39 | this when configuring OpenSSL: |
| 40 | |
| 41 | .. code-block:: console |
| 42 | |
| 43 | $ ./config -Wl,--version-script=openssl.ld -Wl,-Bsymbolic-functions -fPIC shared |
| 44 | |
| 45 | You'll also need to generate your own ``openssl.ld`` file. For example:: |
| 46 | |
| 47 | OPENSSL_1.0.1F_CUSTOM { |
| 48 | global: |
| 49 | *; |
| 50 | }; |
| 51 | |
| 52 | You should replace the version string on the first line as appropriate for your |
| 53 | build. |
| 54 | |
| 55 | Using your own OpenSSL on OS X |
| 56 | ------------------------------ |
| 57 | |
| 58 | To link cryptography against a custom version of OpenSSL you'll need to set |
| 59 | ``ARCHFLAGS``, ``LDFLAGS``, and ``CFLAGS``. OpenSSL can be installed via |
| 60 | `Homebrew`_: |
| 61 | |
| 62 | .. code-block:: console |
| 63 | |
| 64 | $ brew install openssl |
| 65 | |
| 66 | Then install cryptography linking against the brewed version: |
| 67 | |
| 68 | .. code-block:: console |
| 69 | |
| 70 | $ env ARCHFLAGS="-arch x86_64" LDFLAGS="-L/usr/local/opt/openssl/lib" CFLAGS="-I/usr/local/opt/openssl/include" pip install cryptography |
| 71 | |
| 72 | |
| 73 | .. _`Homebrew`: http://brew.sh |
| 74 | .. _`pre-compiled binaries`: https://www.openssl.org/related/binaries.html |