Coze
sqlcipher
Coze | sqlcipher | |
---|---|---|
27 | 10 | |
103 | 5,941 | |
0.0% | 0.8% | |
6.1 | 7.6 | |
about 2 months ago | 10 days ago | |
Go | C | |
BSD 3-clause "New" or "Revised" 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.
Coze
-
JSON Web Proofs
https://cyphr.me/coze#?input={%22pay%22:{%22msg%22:%22Hello,...
-
Hype Will Turn Your Security Key into Junk
We're working on an open source alternative to Passkeys starting with Coze https://github.com/Cyphrme/Coze.
We have not yet published our next steps, but we will soon.
-
Introducing Coze - a cryptographic JSON messaging specification
You can play with Coze here using the online tool. There is also the simple tool.
- Show HN: Coze – cryptographic JSON messaging specification
-
Coze: a cryptographic JSON messaging specification designed for human readability
Base64 also has problems, in particular with canonicalization. This is a problem that I think needs more awareness in the industry. It does seem to recently gained some awareness (See the paper, "Base64 Malleability in Practice")
-
Daily General Discussion - July 10, 2023
Coze is a cryptographic JSON messaging specification designed for human readability.
-
Passage by 1Password
Our website is already using public key authentication using Coze. https://github.com/Cyphrme/Coze. We've been doing public key authentication for around 2 years now. No passwords needed, just public key auth.
-
Passkeys: The Beginning of the End of the Password
On my website, I'm doing authentication via simple public key authentication using Coze.
No passwords. No email. No Google. https://github.com/Cyphrme/Coze
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?
rust-u2f - U2F security token emulator written in Rust
sqlitebrowser - Official home of the DB Browser for SQLite (DB4S) project. Previously known as "SQLite Database Browser" and "Database Browser for SQLite". Website at:
openpgpjs - OpenPGP implementation for JavaScript
SQLite - Official Git mirror of the SQLite source tree
ITCB-master - One Repo to Find Them, and In the Darkness, Bind Them
rust_sqlite - SQLRite - Simple embedded database modeled off SQLite in Rust
OpenSK - OpenSK is an open-source implementation for security keys written in Rust that supports both FIDO U2F and FIDO2 standards.
SQLite3MultipleCiphers - SQLite3 encryption extension with support for multiple ciphers
fido2 - Open-source FIDO server, featuring the FIDO2 standard. https://demo4.strongkey.com/getstarted/#/openapi/fido
litestream - Streaming replication for SQLite.
eth-wizard - An Ethereum validator installation wizard
sql.js - A javascript library to run SQLite on the web.