collective.anonfeedback
This package contains two views, a form that will collect feedback, and view to view the feedback. They are protected by two different permissions, the permission to enter feedback is by default given to everyone, and the permission to view the feedback is by default given to site administrators.
The feedback is stored in var/anonfeedback with each feedback in it’s own file. The reason for this is that if we store the feeback in the ZODB we create a ZODB transaction, and if you are logged in to the site at that point, it will be possible to see who wrote the feedback from the Undo transaction log, and the requirement of this package was explicitly that you should be anonymous even if you forget to log out.
Warning!
Please note that it may still be possible to figure out the posters identity by comparing web-server logs and IP-adresses and times, etc. To achieve true anonymity you must also anonymize the internet access. The purpose of this package is just to make it hard for your boss to figure out who thought his proposal for site color scheme was ugly, not to provide truly anonymous whistleblower access.
Contributors
Lennart Regebro, regebro@gmail.com
Change history
1.0 (2014-03-23)
Original release.
1 maintainer
Metadata
1 maintainer
Release files for collective.anonfeedback 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 |
|---|---|---|---|---|
| collective.anonfeedback-1.0.zip | 16.2 kB | Without provenance | Details for collective.anonfeedback-1.0.zip |
Release files / collective.anonfeedback-1.0.zip
| Download URL | collective.anonfeedback-1.0.zip |
|---|---|
| Size | 16.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
e796e3f2352c8b57fa3691a404b7ae8a31af26f60986987d261e84545c0b13af
|
|
BLAKE2b-256 checksum How to use checksums |
5320edddfe127c49b06990557108464c57da37956c467efc1af2008cd097e2c0
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for collective.anonfeedback 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.
