Guillaume E

This is currently not implemented. However, this could be added as a wrapper on top of the raw LZMA algorithm, like the current [`xz` module](https://github.com/gendx/lzma-rs/blob/master/src/decode/xz.rs).

> > What is the portability story? > > It should be fine for basic pinging functionality, but once you want to implement more complex features, there will be some...

> As indicated, I expected this to automatically checked. No strong opinion however, where are ASCII art examples that would need refactoring? It'd be easier to have an exhaustive list...

> @gendx Is this still uesful to be kept open as a canary? Just rebased this pull request to see if the Clippy workflow now fails.

Looks like the current workflow passed instead of denying the lint, so leaving this PR open until #169 is fixed.

Hello, thanks for the heads up! The current AES implementation is definitely just a textbook placeholder (although with comprehensive correctness unit tests), and `aes-soft` sounds like it could be a...

Thanks for the clarification on ECDSA. Indeed a Cryptography WG would be relevant to coordinate these efforts, looking forward to having one started!

Thanks for the heads up! > I’d call the ECDSA implementation “bleeding edge” at this point but we do hope to both get more eyes on it and improve testing...

I don't think this level of formalism is necessary to understand the issue. It's rather clear that over time changes in any of the dependencies affects reproducibility, and therefore we...

> However a cron job that tests the reproducibility of old commits (maybe just some tags to avoid computational costs) would be useful to track reproducibility issues. This could be...