Tracking issue for next release series

[tarcieri]

This is a tracking issue for the next set of breaking releases which are currently under development on the master branch:

• ascon-hash256
• ascon-xof128
• bash-hash v0.1
• belt-hash v0.2
• blake2 v0.11: code refactoring
• cshake v0.1
• fsb v0.2
• gost94 v0.11
• groestl v0.11
• jh v0.2
• k12 v0.3
• kupyna v0.1
• md2 v0.10
• md4 v0.11
• md-5 v0.11
• ripemd v0.2
• sha1 v0.11
• sha1-checked v0.11: code refactoring
• sha2 v0.11
• sha3 v0.11
• shabal v0.4
• skein v0.2
• sm3 v0.5
• streebog v0.11
• tiger v0.3
• turboshake v0.1
• whirlpool v0.11

[rakshith-ravi]

Is my understanding correct that sha2 v0.11 will support non-finalised hashers to be serialised and deserialised?

Basically:

let mut hasher = Sha256::new();
hasher.update(b"hello ");

// Useful for multi-part uploads where hashing the body in chunks across
// multiple HTTP requests may be required
store_in_redis(hasher);

let mut hasher = get_from_redis();
hasher.update(b"world");

assert_eq!(hasher.finalize(), Sha256::digest(b"hello world"));

If so, how do I help push this forward? The PR for crypto-common v0.2.0 RustCrypto/traits#2276 seems to be merged. Is there anything else I can help with?

[tarcieri]

@rakshith-ravi support was already added in #574

See: https://docs.rs/sha2/0.11.0-rc.5/sha2/struct.Sha256.html#impl-SerializableState-for-Sha256

[rakshith-ravi]

Awesome! Thanks for this!

Btw, I notice it's not a stable release yet. What needs to be done to make it GA? I'm happy to use the RC for the time being - this solves my blocker - but I'm curious if there's anything I can lend a hand towards for helping push this to GA. I've got some time free this weekend if you folks need any assistance.

Once again, thanks for the help!

[tarcieri]

This is the current blocker: RustCrypto/traits#2309

[newpavlov]

I updated the list with current blockers for remaining releases.