Artyom Pavlov

I think it would be nice if pure Rust flif decoder (e.g. [`flif`](https://github.com/dgriffen/flif.rs) crate) will be developed under this organization. What is the organization policy regarding this? (Ideally I would...

@sallar Take a look at [RustCrypto](https://github.com/RustCrypto) organization, it aims to succeed `rust-crypto` crate by creating an ecosystem of crypto-crates, which are `wasm` and (if possible) `no_std` friendly.

AES encryption is implemented in [`aes-safe`](https://docs.rs/aes-soft/0.1.0/aes_soft/) and [`aesni`](https://docs.rs/aesni/0.3.1/aesni/) crates (the latter for now works only on Nightly, stable support will happen after SIMD stabilization), block modes of operation are available...

PBKDF2 is implemented in [`pbkdf2`](https://docs.rs/pbkdf2/0.2.0/pbkdf2/fn.pbkdf2.html) crate. You can use it like this: ```Rust use hmac::Hmac; use sha2::Sha256; pbkdf2::pbkdf2::(password, salt, complexity, &mut output_buf[..n]); ``` CBC encryption with `aes_safe` crate (in future...

Glad to help! If you have all your data in a `Vec` and don't need streaming encryption, than this should do the work: ```Rust // `data` has type `Vec` let...

Ups, I've meant `aes-soft` of course.

Several nitpicks after cursory read, but otherwise looks good to me! - `SHA256_BLOCK_LEN` should be `AES256_BLOCK_LEN` - `.expect("HMAC Key is required.")` is not strictly speaking correct, as HMAC can be...

This crate is unmaintained, it's strongly recommended to use other crates instead. https://rustsec.org/advisories/RUSTSEC-2016-0005.html

Take a look at [RustCrypto](https://github.com/RustCrypto) organization, it does exactly what you've described. It's still work in progress, so some algorithms are missing.

Wat? Crates are completely independent from each other (well, if we exclude dependency on common trait crates to abstract functionality and small utility crates) and published as standalone crates ([sha2](https://crates.io/crates/sha2),...