fido2
Open-source FIDO server, featuring the FIDO2 standard. https://demo4.strongkey.com/getstarted/#/openapi/fido (by StrongKey)
sqlcipher
SQLCipher is a standalone fork of SQLite that adds 256 bit AES encryption of database files and other security features. (by sqlcipher)
fido2 | sqlcipher | |
---|---|---|
1 | 10 | |
203 | 5,966 | |
-0.5% | 1.2% | |
2.0 | 7.6 | |
10 months ago | 22 days ago | |
C | ||
- | GNU General Public License v3.0 or later |
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
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.
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.
fido2
Posts with mentions or reviews of fido2.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2023-05-03.
sqlcipher
Posts with mentions or reviews of sqlcipher.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2024-04-30.
-
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