Introduction
This Zope hotfix fixes CVE 2010-1104.
This hotfix has been tested with Zope instances using Zope 2.8.x - 2.11.x. Users of Zope 2.12 and greater should instead update to the latest corresponding minor revision, which already includes this fix.
Installation
Download the tarball from the PyPI page:
http://pypi.python.org/pypi/Products.Zope_Hotfix_CVE_2010_1104
Unpack the tarball and add a ‘products’ key to the ‘etc/zope.conf’ of your instance. E.g.:
products /path/to/Products.Zope_Hotfix_CVE_2010_1104/Products
and restart. Alternatively, you may copy or symlink the ‘Products’ directory into the ‘Products’ subdirectory of your Zope instance. E.g.:
$ cp -r /path/to/Products.Zope_Hotfix_CVE_2010_1104/Products \ /path/to/instance/Products/
Verifying the Installation
After restarting the Zope instance, check the ‘Control_Panel/Products’ folder in the Zope Management Interface, e.g.:
You should see the ‘Zope_Hotfix_CVE_2010_1104’ product folder there.
Changelog
1.0 (2012-01-18)
Initial release
Metadata
Release files for Products.Zope_Hotfix_CVE_2010_1104 1.0
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 |
|---|---|---|---|---|
| Products.Zope_Hotfix_CVE_2010_1104-1.0.tar.gz | 3.5 kB | Without provenance | Details for Products.Zope_Hotfix_CVE_2010_1104-1.0.tar.gz |
Release files / Products.Zope_Hotfix_CVE_2010_1104-1.0.tar.gz
| Download URL | Products.Zope_Hotfix_CVE_2010_1104-1.0.tar.gz |
|---|---|
| Size | 3.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
8c3ff7b498bb5fb82ef9d00060e09567a0fd8654cfd703fa55284cae51fea3c9
|
|
BLAKE2b-256 checksum How to use checksums |
a12be063f64f95309c28ebdb7b09305cb7b2217e9fc8b0e067c55267574a29cf
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for Products.Zope_Hotfix_CVE_2010_1104 1.0
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.
