PyVEP has been renamed to PyBrowserID
In keeping with the new branding of the protocol, further development of this project will take place under the name “PyBrowserID”:
0.4.0 - 2012-03-13
Renamed from PyVEP to PyBrowserID, in keeping with Mozilla branding.
Audience checking now accepts glob-style patterns as well as fixed audience strings.
Verifier objects now accept a list of audience patterns as their first argument. This is designed to encourage doing the right thing rather than, say, passing in the hostname from the request.
Allowed LocalVerifier to use of a custom JWT parser.
Removed browserid.verify_[remote|local|dummy] since they just cause confusion. You should either accept the defaults provided by the browserid.verify function, or use a full-blown Verifier object.
Split certificate loading and caching into a separate class, in browserid.certificates:CertificatesManager.
Removed the DummyVerifier class in favour of supporting functions in browserid.tests.support.
0.3.2 - 2012-02-03
Fix segfaults on OSX.
Update license to MPL 2.0.
0.3.1 - 2012-01-24
Update the audience-extraction code in RemoteVerifier to support the new-style assertion format; thanks junkafarian.
0.3.0 - 2012-01-06
Support the “new-style” VEP assertion format. This avoids double-b64- encoding and generally results in smaller assertions.
Warn rather than fail if we can’t find the CA certificates. This will help new users get up and running more easily.
Add shortcut functions for verification with the default options. They are vep.verify(), vep.verify_remote(), vep.verify_local(), and vep.verify_dummy().
Add vep.utils.get_assertion_info(), which parses useful information out of an assertion without actually verifying it.
Make LocalVerifier expire cached public keys after 6 hours by default.
Allow LocalVerifier to take a user-specified cache object so that public keys can be stored in e.g. memcached.
Update to the latest issuer-key-fetch protocol (using /.well-known/vep).
Add InvalidIssuerError to report on invalid or untrusted issuers.
Clean up the internal JWT interface. It now uses module-level functions rather than classmethods.
0.2.1 - 2011-12-16
Use M2Crypto for faster DSA operations.
DummyVerifier: fix hex formatting for compatability with jwcrypto.
DummyVerifier: don’t emit FutureWarning on initialisation.
0.2.0 - 2011-12-07
do more validation of the assertion before checking the certificates, to avoid expensive crypto ops for things we know to be invalid.
implement DummyVerifier class to aid in testing, both of this package and of packages that are using PyVEP.
add exception hierarchy in vep.errors, so that calling code can easily tell why verification failed.
0.1.1 - 2011-12-01
add “diresworb.org” to default list of trusted secondaries.
implement additional signature algorithms.
if “hostname/.well-known/host-meta” gives a 404, fall back to “hostname/pk” to find the public key.
0.1.0 - 2011-11-23
initial release.
Metadata
Release files for PyVEP 0.3.2
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 |
|---|---|---|---|---|
| PyVEP-0.3.2.tar.gz | 31.0 kB | Without provenance | Details for PyVEP-0.3.2.tar.gz |
Release files / PyVEP-0.3.2.tar.gz
| Download URL | PyVEP-0.3.2.tar.gz |
|---|---|
| Size | 31.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
ee0749d8ca4ea7f22cec0d2580a02ce4b23571de294a0f6593167a2ddd3c54a3
|
|
BLAKE2b-256 checksum How to use checksums |
dadb10fa8a3a858b7cc35a8b10180565b62d3bdf8aa8f02ced8b18c719f9c799
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for PyVEP 0.3.2
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.