gea-implementation
skipjack.rs
| gea-implementation | skipjack.rs | |
|---|---|---|
| 2 | 1 | |
| 15 | 10 | |
| - | - | |
| 0.0 | 3.8 | |
| almost 2 years ago | over 2 years ago | |
| Rust | Rust | |
| GNU Affero General Public License v3.0 | 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.
gea-implementation
skipjack.rs
-
Rolling your own crypto: Everything you need to build AES from scratch
I think you've misunderstood.
There are at least two separate things are stake here: there's professional software engineering, and then there's hobbyist programming.
Software engineering has been undergoing professionalization (in terms of processes and safety standards) for the last 70 years. It's one of the few ways in which software really is an engineering practice: our standards are written in blood (or fraud), just like every other engineering discipline. In this context, DRYAC and "don't write it in C" are excellent principles: we've successfully professionalized and compartmentalized beyond the need for the bad old ways, except in limited cases (corresponding to domain expertise or specific, legacy requirements).
Then there's hobbyist programming, where you can do whatever you please. I write C for fun. I implement hilariously outdated block ciphers for fun[1]. I couldn't write a web app if my life depended on it. The key understanding with hobbyist programming is that it's (1) adequately disclaimed as not usable in professional contexts, or (2) adheres to the same standards as professional, potentially critical, software engineering.
Open source started as case (1) above, and is slowly turning towards case (2) where it matters. And where it matters is cryptography and, increasingly, memory unsafe code.
In other words: you're more than welcome to build a model train set (I do it), but it doesn't qualify either of us to run a railroad. What qualifies us is learning and performing everything else involved in the safe and normal operation of a modern railroad, including knowing not to build steam engines anymore.
[1]: https://github.com/woodruffw/skipjack.rs
What are some alternatives?
rustic - rustic - fast, encrypted, and deduplicated backups powered by Rust
spacedrive - Spacedrive is an open source cross-platform file explorer, powered by a virtual distributed filesystem written in Rust.
zbox - Zero-details, privacy-focused in-app file system.
ffsend - :mailbox_with_mail: Easily and securely share files from the command line. A fully featured Firefox Send client.
rage - A simple, secure and modern file encryption tool (and Rust library) with small explicit keys, no config options, and UNIX-style composability.
Ockam - Orchestrate end-to-end encryption, cryptographic identities, mutual authentication, and authorization policies between distributed applications – at massive scale.