tursodatabase / tursodatabase/libsql
Switch to SQLCipher cipher
Open
Nobody has claimed this yet.
encryption at rest
enhancement
question
- Dominant language
- C
- Stars
- 17.2k
- Forks
- 531
- Avg merge
- 1h 12m
- Merged PRs (30d)
- 1
Description
We integrated https://github.com/utelle/SQLite3MultipleCiphers into the libSQL source tree, but we should really pick one cipher and stick to that. The best one seems to be SQLCipher.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the current SQLite3MultipleCiphers integration in the libSQL source tree and the requirements for SQLCipher. Determine the affected source and build areas, then define what a complete switch would require, including how the existing cipher integration is removed and how the result is validated.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c, sqlite
- Domain
- databases
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100