SqliteSec
Secure SQLite databases with AES-256 encryption
SqliteSec protects your SQLite databases by encrypting them with industry-standard AES-256 encryption. Share sensitive data safely or work with confidential information without compromising security.
Installation
pip install sqlitesec
Features
- AES-256 encryption - Military-grade security for your databases
- Seamless integration - Drop-in replacement for standard SQLite connections
- Automatic encryption/decryption - Transparent operation with your existing code
- Secure file sharing - Safely send encrypted databases to others
Quick Start
from sqlitesec import SqliteSec
import os
# Initialize with your encryption key
key = os.urandom(32) # Generate a secure 256-bit key
sqs = SqliteSec(key)
# Create and use encrypted database
conn = sqs.connect("secure.db")
cursor = conn.cursor()
# Standard SQLite operations work normally
cursor.execute('CREATE TABLE users (id INTEGER PRIMARY KEY, name TEXT)')
cursor.execute('INSERT INTO users (name) VALUES (?)', ('Alice',))
conn.commit()
# Always close properly to ensure encryption
sqs.close(conn, "secure.db")
Reading Encrypted Data
# Reconnect and read data
conn = sqs.connect("secure.db")
cursor = conn.cursor()
cursor.execute('SELECT name FROM users WHERE id = 1')
user_name = cursor.fetchone()[0]
print(f"User: {user_name}")
sqs.close(conn, "secure.db")
API Reference
SqliteSec(key)
Initialize with encryption key (32 bytes for AES-256).
connect(database_path)
Open encrypted database connection. Returns standard SQLite connection object.
close(connection, database_path)
Properly close connection and ensure data is encrypted.
Security Note: Always use a strong, randomly generated key and store it securely.
Metadata
Release files for sqlitesec 1.0.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 | |
|---|---|---|---|---|
| sqlitesec-1.0.0.tar.gz | 4.5 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| sqlitesec-1.0.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 9.0 kB
Release files / sqlitesec-1.0.0.tar.gz
| Download URL | sqlitesec-1.0.0.tar.gz |
|---|---|
| Size | 4.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
029cbd70c16bfa200eca602797f5cb4c1cce0efdeff638e2e9c539af24e716d3
|
|
BLAKE2b-256 checksum How to use checksums |
20ddece590b9d0942ddc86c568b3544ef90b4e0ca4fc1477cc9ef27f03f13a96
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.12.3
|
Release files / sqlitesec-1.0.0-py3-none-any.whl
| Download URL | sqlitesec-1.0.0-py3-none-any.whl |
|---|---|
| Size | 4.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
e87e40084e74789576ad54646c62bf1abe008f84a12b4d6093ccb16656cfcd33
|
|
BLAKE2b-256 checksum How to use checksums |
4ba2a4d25be783c9b17b3dd40bcde72a3357a01c14babedc5b9b9492ab367460
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.12.3
|
Security for sqlitesec 1.0.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.