github/requests
1
0
Fork 0
Code Issues Pull Requests Actions 2 Packages Projects Releases Wiki Activity

Clarify docs that Requests always uses certs from certifi

Browse Source 
Since commit 0d7de6430e, certifi is always
used for certificates. Certify became a hard dependency of the package
in 628633143d.

Now update the docs to clarify that Request will always use certificates
from certifi.
This commit is contained in:
Jon Dufresne
2018-02-02 15:49:03 -08:00
parent 3c1d36b827
commit 9c0db92249
1 changed files with 7 additions and 8 deletions
Download Patch File Download Diff File Expand all files Collapse all files

15
docs/user/advanced.rst
View File

@@ -274,15 +274,14 @@ If you specify a wrong path or an invalid cert, you'll get a SSLError::
CA Certificates CA Certificates
--------------- ---------------
By default, Requests bundles a set of root CAs that it trusts, sourced from the Requests uses certificates from the package `certifi`_. This allows for users
`Mozilla trust store`_. However, these are only updated once for each Requests to update their trusted certificates without changing the version of Requests.
version. This means that if you pin a Requests version your certificates can
become extremely out of date.
From Requests version 2.4.0 onwards, Requests will attempt to use certificates Before version 2.16, Requests bundled a set of root CAs that it trusted,
from `certifi`_ if it is present on the system. This allows for users to update sourced from the `Mozilla trust store`_. The certificates were only updated
their trusted certificates without having to change the code that runs on their once for each Requests version. When ``certifi`` was not installed, this led to
system. extremely out-of-date certificate bundles when using significantly older
versions of Requests.
For the sake of security we recommend upgrading certifi frequently! For the sake of security we recommend upgrading certifi frequently!