cipher.encryptingstorage
ZODB storage wrapper for encryption of database records. Actually it is doing encryption and compression.
Installation manual with buildout
Follow https://pypi.python.org/pypi/keas.kmi to generate a kek.dat file:
$ git clone https://github.com/zopefoundation/keas.kmi.git
$ cd keas.kmi
$ python2.7 bootstrap.py
$ ./bin/buildout
$ ./bin/runserver &
$ wget https://localhost:8080/new -O kek.dat --ca-certificate sample.pem \
--post-data=""
$ wget https://localhost:8080/key --header 'Content-Type: text/plain' \
--post-file kek.dat -O datakey.dat --ca-certificate sample.pem
Now copy kek.dat and the keys folder to your plone site:
$ cp -pi kek.dat /home/yourname/Plone/training/var/kek.dat $ cp -pri keys /home/yourname/Plone/training/var/dek-storage
Then create a encryption.conf like this in your buildout directory:
[encryptingstorage:encryption] enabled = true kek-path = /home/yourname/Plone/training/var/kek.dat dek-storage-path = /home/yourname/Plone/training/var/dek-storage/
Then edit buildout.cfg and add cipher.encryptingstorage to your eggs:
eggs +=
cipher.encryptingstorage
Now extend your [instance] ( plone.recipe.zope2instance ):
zope-conf-imports =
cipher.encryptingstorage
zope-conf-additional =
<zodb_db main>
cache-size 30000
<encryptingstorage>
config encryption.conf
# FileStorage database
<filestorage>
path ${buildout:buildout_dir}/var/filestorage/Data.fs
blob-dir ${buildout:buildout_dir}/var/blobstorage
</filestorage>
</encryptingstorage>
mount-point /
</zodb_db>
Then run buildout:
$ ./bin/buildout
Remove the generated <zodb_db main> entry in parts/instance/etc/zope.conf:
<zodb_db main>
# Main database
cache-size 30000
# Blob-enabled FileStorage database
<blobstorage>
blob-dir /home/yourname/Plone/training/var/blobstorage
# FileStorage database
<filestorage>
path /home/yourname/Plone/training/var/filestorage/Data.fs
</filestorage>
</blobstorage>
mount-point /
</zodb_db>
Run the tests/develop
$ virtualenv -p /usr/bin/python2.7 --no-site-packages . $ ./bin/pip install -r requirements.txt $ ./bin/buildout $ ./bin/test -v1
CHANGES
1.1 (2016-04-22)
Add encryption for blobstorage. [pcdummy]
1.0.0 (2012-04-06)
0.1.0 (2012-02-14)
Initial release as a separate package.
Metadata
Release files for cipher.encryptingstorage 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 | Actions |
|---|---|---|---|---|
| cipher.encryptingstorage-1.1.tar.gz | 16.4 kB | Without provenance | Details for cipher.encryptingstorage-1.1.tar.gz |
Release files / cipher.encryptingstorage-1.1.tar.gz
| Download URL | cipher.encryptingstorage-1.1.tar.gz |
|---|---|
| Size | 16.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
4c1555ca0b68177d10ef59ebcc8f4055b8abaf9f51e869fea23afe3981c6c4b8
|
|
BLAKE2b-256 checksum How to use checksums |
50508802f084731704e953324505376d9029ca15c491fcc43e8da62c82dd1443
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for cipher.encryptingstorage 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.
To learn more about protecting yourself from malicious actors, visit our package security documentation.