Documentation
See https://wiki.mozilla.org/Apps/WebApplicationReceipt/SigningService
Dev and testing
Create a virtualenv of your choosing and activate it:
virtualenv websigning source websigning/bin/activate
Or using virtualenvwrapper:
mkvirtualenv websigning
Install the dependencies:
python setup.py develop
Run tests:
python setup.py nosetests
When testing, you may see output along the lines of:
“InsecurePlatformWarning: A true SSLContext object is not available.”
This seems to be a feature of newer versions of the request module. This can be solved by installing by running:
pip install requests[security]
1 maintainer
Metadata
1 maintainer
Release files for websigning 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 |
|---|---|---|---|---|
| websigning-0.1.tar.gz | 19.4 kB | Without provenance | Details for websigning-0.1.tar.gz |
Release files / websigning-0.1.tar.gz
| Download URL | websigning-0.1.tar.gz |
|---|---|
| Size | 19.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
0b81217fb7960445f2a11be9c711abaf26fda6b6d950ee2d000271deefac53c8
|
|
BLAKE2b-256 checksum How to use checksums |
0a14cea39ff74dea5f56a017fb601cf134c6ec78166b86d7c95c92990cadf053
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for websigning 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.
