sqlitebrowser / sqlitebrowser/sqlitebrowser
SQLCipher entering passphrase and encoded raw key not working
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?
Hi, I was trying out the SQLCipher functionality of sqlitebrowser and had some weird behaviour.
I created a Test.db (attached with .env, default SQLCipher 4 values) with a raw key (0x61) and tried to open it using the - hexdecoded - passphrase (a).
I also tried to insert 0x00 before and after raw key until 64 characters, because from Pragma Key Documentation I was not sure if the application is responsible of passing exactly 64 characters.
What did you expect to see?
As far as I understood it should be possible to either enter the rawkey or the password with sqlitebrowser(SQLCipher). Did I miss something?
What did you see instead?
Could not access Database.
Useful extra information
The info below often helps, please fill it out if you're able to. :)
What operating system are you using?
- Windows: ( version: Windows 10 64bit )
- Linux: ( distro: 11.2.1 )
- macOS: ( version: ___ )
- Other: ___
What is your DB4S version?
- 3.12.2
- 3.12.1
- 3.12.0
- 3.11.x
- Other: ___
Did you also
- [] Try out the latest nightly version: https://github.com/sqlitebrowser/sqlitebrowser#nightly-builds
- Search for an existing similar issue: https://github.com/sqlitebrowser/sqlitebrowser/issues?utf8=%E2%9C%93&q=is%3Aissue%20
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 report with the attached Test.zip on DB4S 3.12.2, using the raw key and passphrase described in the issue. Read the linked SQLCipher PRAGMA key documentation to compare the expected key handling with the application's behavior. Done means the supplied encrypted database opens successfully with the supported raw-key or passphrase input.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, sqlite
- Domain
- database
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100