sqlitebrowser / sqlitebrowser/sqlitebrowser
Encrypted files that were never encrypted
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 24.6k
- Forks
- 2.4k
- Avg merge
- 3d 49m
- Merged PRs (30d)
- 3
Description
Details for the issue
What did you do?
Tried to open an sqlite file.
What did you expect to see?
An opened database.
What did you see instead?
Was asked for an encryption key. I have never encrypted any files ever. This happened with several files
Useful extra information
DB4S v3.12.2 [built for x86_64-little_endian-lp64] on Linux Mint 20.1 (linux/5.4.0-88-generic) [x86_64]
using SQLCipher Version 4.4.3 community (based on SQLite 3.34.1)
and Qt 5.12.8
Contributor guide
No contributing guide indexed for this repository
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 reproducing the prompt when opening the reported SQLite files under DB4S v3.12.2 with SQLCipher 4.4.3 on Linux Mint 20.1, then trace the database-opening and encryption-prompt path. Done means unencrypted SQLite files open without requesting a key, with the behavior verified across the reported files.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, sqlite
- Domain
- database, desktop
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100