3 ms·
Rust code already exclusively uses rust ports of the library. There are a couple competing ones [1][2], but I couldn't even find rust bindings for the official
by wongarsu 4y ago
Rust code already exclusively uses rust ports of the library. There are a couple competing ones [1][2], but I couldn't even find rust bindings for the official C library. The ecosystem has a bit of a fetish for pure rust dependencies where possible, and this vulnerability seems to vindicate that stance.
I don't think any of those are published as libraries usable by other languages, but doing that would be less than a hundred lines for defining a C interface.
1: https://lib.rs/crates/sha3 https://lib.rs/crates/sha3
2: https://lib.rs/crates/tiny-keccak https://lib.rs/crates/tiny-keccak
- oconnor663 4y agoI maintain some Rust bindings to the official implementation here: https://crates.io/crates/kangarootwelve_xkcp https://crates.io/crates/kangarootwelve_xkcp. I've published an update with today's patch (https://github.com/XKCP/K12/commit/27a84ecb811200990add07a047214f4ee7f77d48 https://github.com/XKCP/K12/commit/27a84ecb811200990add07a04...). That said, I don't know whether those overflows were exploitable with K12.