sqlcipher
rust_sqlite
Our great sponsors
sqlcipher | rust_sqlite | |
---|---|---|
9 | 9 | |
5,922 | 1,058 | |
1.2% | - | |
6.3 | 0.0 | |
about 1 month ago | almost 2 years ago | |
C | Rust | |
GNU General Public License v3.0 or later | MIT License |
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.
sqlcipher
-
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.
-
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
rust_sqlite
- Writing a SQLite clone from scratch in C
- SQLite the only database you will ever need in most cases
- SQLRite – SQLite clone from scratch in Rust
-
What would SQLite look like if written in Rust? — Part 2
You may have noticed that throughout the entire code I am making reference to a SQLRiteError type. That is an error type I defined as an enum using the thiserror crate, that is a super easy to use library that provides a convenient derive macro for the standard library’s std::error::Error trait. If you check the commits in the github repository, you may notice that I first wrote my own implementation of the std::error::Error trait. But then I bumped into this trait, that basically takes care of a lot of the boiler plate, and let’s face it, the code looks super clean! This is our error module so far, located in src/error.rs .
-
New chapter on the series - Writing a SQLite clone from scratch in Rust
Also check out the github repo: https://github.com/joaoh82/rust_sqlite
- What would SQLite would look like if written in Rust?
- SQLite Clone from Scratch in Rust
-
What would SQLite look like if written in Rust? — Part 1
I assume that if you are trying to follow this and writing some code along with me you can manage to create an empty Rust project on your own. Just to be clear this is what I did to start: cargo new rust_sqlite --bin . But again, you can find all the code on Github.
-
What would SQLite look like if written in Rust? — Part 0
View on Github (pull requests are welcome)
What are some alternatives?
sqlitebrowser - Official home of the DB Browser for SQLite (DB4S) project. Previously known as "SQLite Database Browser" and "Database Browser for SQLite". Website at:
temporal_tables - Temporal Tables PostgreSQL Extension
SQLite - Official Git mirror of the SQLite source tree
rustyline - Readline Implementation in Rust
SQLite3MultipleCiphers - SQLite3 encryption extension with support for multiple ciphers
medium-unlimited - A browser extension to read medium.com articles for free without membership.
litestream - Streaming replication for SQLite.
llvm-cbe - resurrected LLVM "C Backend", with improvements
sql.js - A javascript library to run SQLite on the web.
rqlite - The lightweight, distributed relational database built on SQLite.
beekeeper-studio - Modern and easy to use SQL client for MySQL, Postgres, SQLite, SQL Server, and more. Linux, MacOS, and Windows.
chiselstrike - ChiselStrike abstracts common backends components like databases and message queues, and let you drive them from a convenient TypeScript business logic layer