ssl_sni
ssl_sni provides a module similar to the Python 2.7 builtin module ssl with the Server Name Indication (SNI) extension. In particular the wrap_socket function has the extra parameter server_hostname to provide a hostname via SNI to the server.
ssl_sni is built on top of the pyOpenSSL and pyasn1 modules. In other words it is a pure python module that does not make any calls directly (not through pyOpenSSL) to the OpenSSL.
For now the subset of the ssl module provided is that required by mercurial and httpplus (used by mercurial). If you have requests for specific other features please file a bug.
Project Page
The project page is here.
Metadata
Release files for ssl_sni 0.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| ssl_sni-0.1.tar.gz | 4.1 kB | Without provenance | Details for ssl_sni-0.1.tar.gz |
Release files / ssl_sni-0.1.tar.gz
| Download URL | ssl_sni-0.1.tar.gz |
|---|---|
| Size | 4.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
6adfb388e70e147768c4fc980824440e53ec1ce251b3e3a460571395d4975dcb
|
|
BLAKE2b-256 checksum How to use checksums |
eb0583f722dd59a72276c40246e4cc2f64581588b68975b05b5a3902ec445f40
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for ssl_sni 0.1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.