SQLite3MultipleCiphers
sqlcipher
| SQLite3MultipleCiphers | sqlcipher | |
|---|---|---|
| 4 | 10 | |
| 340 | 5,941 | |
| - | 1.5% | |
| 7.5 | 7.6 | |
| about 1 month ago | 6 days ago | |
| C | C | |
| MIT License | GNU General Public License v3.0 or later |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
SQLite3MultipleCiphers
- Show HN: Roast my SQLite encryption at-rest
-
C# program not able to open or connect to an encrypted SQLite Database
DB4S provides only one algorithm based on official SQLite cipher. You can encrypt your database with another in SQLiteStudio or sqlite-gui (I'm an author). Both applications use SQLite3 Multiple Ciphers-library.
-
Sensitive data
Popular SQLite editors e.g. DB4S (supports only SQL Cipher) and SQLiteStudio (SQLCipher and perhaps anothers via plugin) can work with encrypted databases. My sqlite-gui support 5 ciphers through SQLite3 Multiple Ciphers.
-
Connecting to a sqlite database, but encrypting it at rest
My choice is https://github.com/utelle/SQLite3MultipleCiphers/ :)
sqlcipher
-
Show HN: Roast my SQLite encryption at-rest
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
-
Basic Security Practices for SQLite: Safeguarding Your Data
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:
-
What is the best way to store data?
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.
-
Passkeys: The Beginning of the End of the Password
> 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
-
Injecting (cryptographic) secrets into automated software release build pipelines?
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.
-
I made an app just to say F%$K to LastPass
That's not true. There are wonderful open source projects ensuring that layer. https://github.com/sqlcipher/sqlcipher for example.
-
Connecting to a sqlite database, but encrypting it at rest
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.
- SQLite the only database you will ever need in most cases
-
Encrypted sqLite
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
What are some alternatives?
esp32_arduino_sqlite3_lib - Sqlite3 Arduino library for ESP32
sqlitebrowser - Official home of the DB Browser for SQLite (DB4S) project. Previously known as "SQLite Database Browser" and "Database Browser for SQLite". Website at:
SQLite - Official Git mirror of the SQLite source tree
sqlite-gui - Lightweight SQLite editor for Windows
rust_sqlite - SQLRite - Simple embedded database modeled off SQLite in Rust
sqleet - SQLite3 encryption that sucks less
litestream - Streaming replication for SQLite.
SQLite-ICU-MinGW - Building SQLite and SQLiteODBC on Windows with ICU and other extensions using MSVC Build Tools and MSYS2/MinGW
sql.js - A javascript library to run SQLite on the web.
sqlite-createtable-parser - A parser for SQLite create table sql statements.
beekeeper-studio - Modern and easy to use SQL client for MySQL, Postgres, SQLite, SQL Server, and more. Linux, MacOS, and Windows.