21 comments (21 comments)8 reactions (8 reactions)0 assignees (0 assignees)C7,000 stars (7,000 stars)1,105 forks (1,105 forks)batch import
enhancementhelp wanted
Description
Some scenarios need to support db encryption, so we need encryption support.
Contributor guide
- Tech stack
- gosqlite
- Domain
- backenddatabasesecurity
- Issue type
- feature
- DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
- 5
- Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
- over 1 week
- Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
- stale
- ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
- unclear
- Prerequisites
- Go programmingSQLite internalsencryption conceptsCGo
- Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
- 15
- Research direction
- Review the 21 comments in the issue to understand prior discussion and any attempted solutions. Investigate SQLite encryption extensions like SQLCipher or SEE (SQLite Encryption Extension). Examine the repo's current CGo integration to see how native libraries are linked. Look at existing forks or PRs in this repo that attempt encryption support. Consider cross referencing how other Go SQLite drivers (e.g., modernc.org/sqlite) implement encryption. The maintainer's stance is unclear, so contributing would require proposing a design and getting maintainer approval.