This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author Sebastian.Noack
Recipients Sebastian.Noack
Date 2020-01-21.09:32:50
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1579599170.77.0.875579101001.issue39408@roundup.psfhosted.org>
In-reply-to
Content
SQLCipher is industry-standard technology for managing an encrypting SQLite databases. It has been implemented as a fork of SQLite3. So the sqlite3 corelib module would build as-is against it. But rather than a fork (of this module), I'd rather see integration of SQLCiper in upstream Python. I'm happy to volunteer if this changes have any chance of landing.

By just adding 2 lines to the cpython repository (and changing ~10 lines), I could make SQLCipher (based on the current sqlite3 module) available as a separate module (e.g. sqlcipher or sqlite3.cipher). However, IMO the ideal interface would be sqlilte3.connect(..., sqlcipher=True).

Any thoughts?
History
Date User Action Args
2020-01-21 09:32:50Sebastian.Noacksetrecipients: + Sebastian.Noack
2020-01-21 09:32:50Sebastian.Noacksetmessageid: <1579599170.77.0.875579101001.issue39408@roundup.psfhosted.org>
2020-01-21 09:32:50Sebastian.Noacklinkissue39408 messages
2020-01-21 09:32:50Sebastian.Noackcreate