traits
ecies-ed25519
Our great sponsors
traits | ecies-ed25519 | |
---|---|---|
4 | 1 | |
533 | 30 | |
0.9% | - | |
9.2 | 0.0 | |
7 days ago | over 2 years ago | |
Rust | Rust | |
- | 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.
traits
-
RustCrypto Release Announcements: `aead` v0.4, `cipher` v0.3, `crypto` v0.2, `elliptic-curve` v0.9, `ecdsa` v0.11
For ECIES that'd probably be something like HPKE. HPKE isn't specific to ECC though, and is defined in terms of a KEM, so the first step there would probably be defining KEM traits which would allow you to plug in ECDH or potentially a post-quantum algorithm or RSA.
-
The last and next year of image-rs
No need for eternal stability. It would be indeed nice to get the API right the first time, but in practice it's borderline impossible to do. It's fine for trait crates to introduce breaking changes from time to time, especially for pre-1.0 ones. For prior art you can take a look at rand_core or RustCrypto trait crates.
-
What’s everyone working on this week (8/2021)?
I finally dusted off my barely-working git hosting solution and added a basic user account system. It took me some time to understand how exactly I was supposed to use password-hash in combination with my hashing function of choice, as well as with the DB. Using sqlx together with Rocket turned out to be somewhat easy once I figured out that I should disregard the built-in database support, since it's seemingly incompatible with sqlx.
-
Go vs Rust for crypto implementations
The main difference between those two languages, I think you should look at, is power of type system. A good type system allows to encode various invariants checked at compile time, help with interoperability, and even improve performance a bit (e.g. by eliminating runtime-checks). In this regard Rust is far, far ahead of Go in my opinion and continues to improve in this regard (e.g. soon we will have const generics). For example, in RustCrypto we have trait crates which contain "interfaces" of several algorithm types. Almost all algorithm implementations in this org (and some third-party implementations) are implemented in terms of those traits, which means you can easily swap algorithms with each other and combine them like Lego blocks, without diving deep into source code. This property is especially important if you want to support less common algorithms (e.g. regional standards or newly developed algorithms).
ecies-ed25519
-
RustCrypto Release Announcements: `aead` v0.4, `cipher` v0.3, `crypto` v0.2, `elliptic-curve` v0.9, `ecdsa` v0.11
For example, would consider housing ECIES (https://github.com/phayes/ecies-ed25519) under the RustCrypto organization?
What are some alternatives?
rav1e - The fastest and safest AV1 encoder.
ed25519-dalek - Fast and efficient ed25519 signing and verification in Rust.
tink-rust - Rust port of Tink cryptography library
edgetk - 🔒 EC Integrated Security Suite written in Go
nlprule - A fast, low-resource Natural Language Processing and Text Correction library written in Rust.
Halite - High-level cryptography interface powered by libsodium
mos - An assembler, code formatter, language server and debug adapter for the MOS 6502 CPU.
fastcrypto - Common cryptographic library used in software at Mysten Labs.
google-hashcode-template - Google Hashcode Rust Template
signatures - Cryptographic signature algorithms: DSA, ECDSA, Ed25519
meta - Meta-crates of the RustCrypto project
SecurityDriven.Winter - Cloud-Scale Cryptography.