The rpctools package provides client libraries for working with RPC services with enhanced SSL support.
Currently the only protocol implemented is JSON-RPC. The enhanced SSL support is simply that these libraries can present client certificates for authentication and can be set up to require a trusted SSL connection with the server (validating CA and hostname matches).
2 maintainers
Metadata
2 maintainers
Release files for rpctools 0.3.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 |
|---|---|---|---|---|
| rpctools-0.3.1.tar.gz | 16.2 kB | Without provenance | Details for rpctools-0.3.1.tar.gz |
Release files / rpctools-0.3.1.tar.gz
| Download URL | rpctools-0.3.1.tar.gz |
|---|---|
| Size | 16.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
92c19f007e14a24bc32c9df0d6822edb8dc4a6bb6ecd6000818e1f1fd4db4315
|
|
BLAKE2b-256 checksum How to use checksums |
91f94d15d6e654b031a4f5799d7d2f327a07be0c2022c3e9572dde02d59077ba
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for rpctools 0.3.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.
