tursodatabase / tursodatabase/libsql
Users, access restrictions, GRANT etc
Open
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 17.2k
- Forks
- 531
- Avg merge
- 1h 12m
- Merged PRs (30d)
- 1
Description
sqlite has no access restrictions, it is assumed that anyone with access to the OS, has access to the data. In a distributed system, we might want to add some security features, like authentication, authorization. RBAC etc.
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
No files, tests, or entry points are named. Start by reviewing the distributed-system security architecture and existing SQLite integration, then define the authentication, authorization, and RBAC scope; done should mean the agreed security features are implemented and validated.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- sqlite
- Domain
- authentication, authorization, databases, distributed-systems, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100