pyramid_clamav
Pyramid tween which checks file uploads for viruses using clamav.
You need to have a running clamav installation on your system to which the tween can connect via a unix socket. You can set the socket path in your config (pyramid_clamav.socket), but the defaults should work on most systems.
If you want to deactivate scanning (i.e. for testing or your local development environment), you can set pyramid_clamav.debug to a value. Then flash- and logmessages are generated if there was a file upload and clamav is not properly configured.
If a virus was found, the file is removed from the request. The field which was used to upload the file should handle it like no file was uploaded.
A flashmessage is presented to the user stating that a file contained a virus and it has been removed.
It should also work for multiple files.
This project was conceived by Daniel Havlik (dh@gocept.com).
pyramid_clamav
0.9 (2022-03-04)
Ignore csrf tokens which look like base64 encoded files.
0.8 (2021-09-17)
Remove Python 2 support.
Check application/json requests for viruses.
0.7 (2020-01-10)
Bugfix: Nonetype object has no attribute get
0.6 (2020-01-10)
Add compatability to Python 3.
Retry connection to clamd if it is busy.
0.5 (2013-12-20)
When collecting file uploads from the request, check for file-like objects instead of instances of exact type file.
0.4 (2013-12-19)
Fix small issue when the value for pyramid_clamav.debug is not configured.
0.3 (2013-12-19)
pyramid_clamav.debug can now be set in config. If enabled AND clamav is not configured, it will generate a flash message when a file upload was found, but the file will not be touched. Additionally errors are logged at startup and on file uploads.
0.2 (2013-12-17)
Fixed setup.py to contain locale directory.
0.1 (2013-12-17)
Initial release.
2 maintainers
Metadata
2 maintainers
Release files for pyramid-clamav 0.9
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 |
|---|---|---|---|---|
| pyramid_clamav-0.9.tar.gz | 6.8 kB | Without provenance | Details for pyramid_clamav-0.9.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| pyramid_clamav-0.9-py3-none-any.whl | Python 3 | none | any | Details for pyramid_clamav-0.9-py3-none-any.whl |
Total release size: 13.5 kB
Release files / pyramid_clamav-0.9.tar.gz
| Download URL | pyramid_clamav-0.9.tar.gz |
|---|---|
| Size | 6.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
e3c54a4558d7219108737b4da0aae0d2d74d6b6c4725d3a827794022e6640c26
|
|
BLAKE2b-256 checksum How to use checksums |
cbee45503362b9b84003174befada06801686eff931e659d7f73156e463f6270
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.7.1 importlib_metadata/4.8.2 pkginfo/1.8.2 requests/2.26.0 requests-toolbelt/0.9.1 tqdm/4.62.3 CPython/3.8.12
|
Release files / pyramid_clamav-0.9-py3-none-any.whl
| Download URL | pyramid_clamav-0.9-py3-none-any.whl |
|---|---|
| Size | 6.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
2c01aca31ac3033e8370a678f1e6609f9e8496b2e3f3895b01f702816c3e2009
|
|
BLAKE2b-256 checksum How to use checksums |
98e3880f9153f9564107aa0d76e6c924fe7ab3f5aea293627e13003d9ab67030
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.7.1 importlib_metadata/4.8.2 pkginfo/1.8.2 requests/2.26.0 requests-toolbelt/0.9.1 tqdm/4.62.3 CPython/3.8.12
|
Security for pyramid-clamav 0.9
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.
