pyramid_csrf_multi_scheme
This package enables two separate cookie tokens on each request, bound to the scheme:
a SECURE HTTPS only cookie
a mixed-use insecure http token (which is also available on https).
If the current scheme is HTTPS:
only the SECURE HTTPS token will be considered
HOWEVER calls to generate a new token will reset both the SECURE HTTPS and the insecure http tokens.
If the current scheme is insecure http:
the SECURE HTTPS tokens are ignored as they are not even available, and only the insecure http token is considered.
Python Versions
This package is currently supported under Python2.7 and 3.8; other 3.x versions may work.
This package should work on Pyramid1.x and 2.x
Why?
If an application supports both HTTP and HTTPS endpoints, this package simplifies isolating the CSRF data from both.
Is this necessary?
I’m not sure, but have decided to err on the side of caution.
HTTP traffic is sent in plaintext and capable of being intercepted by a man-in-the-middle or network packet sniffing.
It seems plausible that someone might read a csrf token via HTTP and use that in attempts to compromise HTTPS endpoints in a mixed use environment.
A better option is to only use HTTPS tokens and forms - but that is not always an option.
debugtoolbar support!
just add to your ENVIRONMENT.ini file, or similar application configuration.
debugtoolbar.includes = pyramid_csrf_multi_scheme.debugtoolbarTthe debugtoolbar will now have a CSRFMultiScheme panel that has the following info:
configuration info on the cookie names
incoming request csrf values
outgoing response csrf values
License
Most of this is just code lightly edited from Pyramid, and therefore available under Pyramid’s licensing terms.
1 maintainer
Metadata
1 maintainer
Release files for pyramid-csrf-multi-scheme 0.1.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 | |
|---|---|---|---|---|
| pyramid_csrf_multi_scheme-0.1.1.tar.gz | 9.6 kB | Without provenance | Details |
Release files / pyramid_csrf_multi_scheme-0.1.1.tar.gz
| Download URL | pyramid_csrf_multi_scheme-0.1.1.tar.gz |
|---|---|
| Size | 9.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
f801d5e882ee1ecf4599f7b93a700d93cae22fb7700abbda003fea339cf9d391
|
|
BLAKE2b-256 checksum How to use checksums |
9833c2c41fc84f81bd8e709213a9a2274cc50654c69b805583a225f7dbb63c6d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.2.0 pkginfo/1.5.0.1 requests/2.24.0 setuptools/47.1.0 requests-toolbelt/0.9.1 tqdm/4.50.2 CPython/3.8.5
|
Security for pyramid-csrf-multi-scheme 0.1.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.
