tursodatabase / tursodatabase/libsql
Expose setting reserver_bytes via libsql and also in bindings
Open
Nobody has claimed this yet.
encryption at rest
- Dominant language
- C
- Stars
- 17.2k
- Forks
- 531
- Avg merge
- 1h 12m
- Merged PRs (30d)
- 1
Description
For Turso Cloud encryption to work, the existing dbs need to have specific reserved bytes set and only then upload can work.
We need to expose this setting via libsql and also in SDKs, so that users can easily upload existing dbs in any environment (like opsqlite on devices)
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 locating the existing reserved-bytes setting in libsql and the binding or SDK entry points that expose database configuration. Trace how an existing database is opened and uploaded, then verify that users can set reserver_bytes through libsql and the bindings for the environments described.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c, sqlite
- Domain
- databases
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100