sqlcipher VS sqlitebrowser

How do you feel yours compares with (say) SQLCipher, which is very popular and keeps fairly close to the upstream SQLite releases?

* https://www.zetetic.net/sqlcipher/

* https://github.com/sqlcipher/sqlcipher

Their most recent release (v4.5.7) is based upon SQLite v3.45.3, which is the latest version of SQLite:

* https://github.com/sqlcipher/sqlcipher/releases/tag/v4.5.7

SQLite, while versatile and easy to use, does not include built-in support for encryption, leaving the data at rest potentially vulnerable. To address this, external tools such as the SQLite Encryption Extension (SEE) or open-source projects like SQLCipher can be employed to encrypt the database file. This process can be achieved through the following steps:

I am personally using SQLite for a project that has been ordered by some future clients and it would perfectly suit your case. I strongly recommend it. Moreover, you can encrypt your entire db is you use this.

> Cloud sync (encrypted!) is important because your average user needs that convenience and durability of authenticator

Local-only iOS Codebook [1] sync (open-source encrypted! by SQLCipher [2]) provides convenience, durability, transparency, decentralization and fewer supply chain dependencies.

[1] https://www.zetetic.net/codebook

[2] https://github.com/sqlcipher/sqlcipher

One option that I have been considering is creating a simple, encrypted SQL database (like SQLite & SQLcipher combo), that could be used to store & retrieve crypto secrets required in the release build pipeline. To manipulate this database, one needs to provide a password. This solution could be implemented as a microservice running on the build server, for example, in a dedicated docker container. To trigger a new release build, the user with the correct credentials could access the build server over our local network, and, if in a possession of the correct password required to decrypt the crypto database, trigger a release build.

That's not true. There are wonderful open source projects ensuring that layer. https://github.com/sqlcipher/sqlcipher for example.

No, SQLCipher takes another approach. They modify the source of SQLite's pager with numerous code blocks in order to "hook in" the encryption code. Compare this SQLCipher code to the original SQLite code.

Your options are use SQLCipher to transparently encrypt the entire DB file on the device, or your have your app handle the encryption/decryption of each record during each read/write operation. If AES-256 isn't a hard requirement, encrypting at the record level is way easier with libsodium secretbox

We have a spread of different GitHub Actions based workflows that do stuff whenever a PR is proposed or merged:

https://github.com/sqlitebrowser/sqlitebrowser/tree/master/....

Most of those are oriented around building packages for various OS's (Linux, macOS, Windows) so people can try the latest code.

While there are some tests, they're more like extremely basic sanity tests and don't rely on Docker.

Those tests rely on whichever version of SQLite was downloaded and compiled into the GUI (as per above code snippet).

---

That being said, that's for the client side GUI application. There's a server side of things too (https://github.com/sqlitebrowser/dbhub.io -> dbhub.io) that does use docker for it's automated tests:

https://github.com/sqlitebrowser/dbhub.io/tree/master/.githu...

Those are integration tests though (eg "make sure we didn't bust communication with our cli", "make sure our go library still works 100% with the server"), and a reasonably decent set of End to End (E2E) tests of the web interface using Cypress.

---

Does that help? :)

Do you know about SQLite DB Browser ? It's a multi platform application that would perfectly fit your use case :).

https://sqlitebrowser.org/

Someone gave you a sqlite database. You probably started to think to install a program like sqlitebrowser, but only to view and read the data. Don't bother, you can use this extension instead.

Try https://sqlitebrowser.org/ it’s great for local use and training purposes

You can see how the db file looks for the app using https://sqlitebrowser.org/

If you want to fiddle with SQLite and don't need all the power herein, I recommend DB Browser for SQLite.

https://sqlitebrowser.org/

Hello y'all. This is my first post here. I'm learning SQL with the Northwind database. When I run a "big" query, like "SELECT * FROM Customers" the application crashes. I noticed this only happens when I run a general query, for example, if I run something more specific (and, by the hand "smaller") it doesn't happen. So, I thought it could be related to the size of the query. But I'm a total beginner so idk. It doesn't happen every time I try to use it, but still, this is frustrating. If there's no solution, what other SQL application can I use to keep learning? I found something on GitHub but this is for an older macOS version.