./security/py-truststore, Verify certificates using native system trust stores

[ CVSweb ] [ Homepage ] [ RSS ] [ Required by ] [ Add to tracker ]


Branch: CURRENT, Version: 0.10.0, Package name: py312-truststore-0.10.0, Maintainer: pkgsrc-users

Truststore is a library which exposes native system certificate stores (ie
"trust stores") through an ssl.SSLContext-like API. This means that Python
applications no longer need to rely on certifi as a root certificate store.
Native system certificate stores have many helpful features compared to a
static certificate bundle like certifi:

* Automatically update certificates as new CAs are created and removed
* Fetch missing intermediate certificates
* Check certificates against certificate revocation lists (CRLs) to avoid
monster-in-the-middle (MITM) attacks
* Managed per-system rather than per-application by a operations/IT team
* PyPI is no longer a CA distribution channel


Master sites:

Filesize: 24.229 KB

Version history: (Expand)


CVS history: (Expand)


   2024-11-03 21:01:05 by Adam Ciarcinski | Files touched by this commit (2) | Package updated
Log message:
py-truststore: updated to 0.10.0

0.10.0

Added support for macOS 10.13 and earlier using the SecTrustEvaluate API. Note \ 
that this API doesn't return fine-grained errors like SecTrustEvaluateWithError \ 
(requires macOS 10.14+).
Added SSLContext.set_default_verify_paths() method.
Changed method for disabling hostname verification for macOS and Windows. \ 
Previously would ignore hostname verification errors if \ 
SSLContext.check_hostname was False. Now for both macOS and Windows the \ 
certificate verification policy is configured to not check certificate hostname. \ 
This should have no effect on users.
   2024-10-14 08:46:10 by Thomas Klausner | Files touched by this commit (325)
Log message:
*: clean-up after python38 removal
   2024-08-22 12:07:23 by Adam Ciarcinski | Files touched by this commit (2) | Package updated
Log message:
py-truststore: updated to 0.9.2

0.9.2

Fixed an issue where implementations supporting Python 3.10 but not the peer \ 
certificate chain APIs would fail during the handshake instead of when importing \ 
the truststore module. The module now raises an error immediately instead of on \ 
first handshake. This was added for the GraalPy implementation specifically, but \ 
there may be others.
   2024-05-07 05:50:18 by Adam Ciarcinski | Files touched by this commit (2) | Package updated
Log message:
py-truststore: updated to 0.9.1

0.9.1

Fixed an issue for CPython 3.13 where ssl.SSLSocket and ssl.SSLObject \ 
certificate chain APIs would return different types.
   2024-04-30 14:44:19 by Adam Ciarcinski | Files touched by this commit (2) | Package updated
Log message:
py-truststore: updated to 0.9.0

0.9.0

Added support for Python 3.13.
Fixed loading additional certificates on macOS.
Changed error message for Windows when peer offers no certificates and \ 
verification is enabled. Previously was IndexError, now is \ 
SSLCertVerificationError.
   2023-10-28 21:57:26 by Thomas Klausner | Files touched by this commit (516) | Package updated
Log message:
python/wheel.mk: simplify a lot, and switch to 'installer' for installation

This follows the recommended bootstrap method (flit_core, build, installer).

However, installer installs different files than pip, so update PLISTs
for all packages using wheel.mk and bump their PKGREVISIONs.
   2023-09-08 13:59:33 by Adam Ciarcinski | Files touched by this commit (4) | Package updated
Log message:
py-truststore: added version 0.8.0

Truststore is a library which exposes native system certificate stores (ie
"trust stores") through an ssl.SSLContext-like API. This means that Python
applications no longer need to rely on certifi as a root certificate store.
Native system certificate stores have many helpful features compared to a
static certificate bundle like certifi:

* Automatically update certificates as new CAs are created and removed
* Fetch missing intermediate certificates
* Check certificates against certificate revocation lists (CRLs) to avoid
  monster-in-the-middle (MITM) attacks
* Managed per-system rather than per-application by a operations/IT team
* PyPI is no longer a CA distribution channel