Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
LoadingALIAS
searching Neon…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
6 ms
·
1.
▲
Show HN: Rscrypto 0.4 treats constant-time as a release gate
(github.com)
1 points
by
LoadingALIAS
3mo ago
|
0 comments
2.
▲
by
LoadingALIAS
3mo ago
I thought it was important to share that v0.4.0 is now validated as constant-time via dudect, BINSEC, and manually/heuristic validation. We also closed Wycheproofs for the primitives that can use them and see perf wins in Blake3, RSA,
3.
▲
by
LoadingALIAS
3mo ago
Karolin, I’ll answer this directly, and try to stay on track, because several claims here are materially wrong. First things first, I am not claiming I've had any third-party audit; I'm not claiming I've been FIPS validated,
4.
▲
by
LoadingALIAS
4mo ago
The SHA2 variants DO share the compression layer where I felt it mattered: - SHA-224 uses the SHA-256 compression kernels w/ different IV/output truncation. - SHA-384 and SHA-512/256 use the SHA-512 compression kernels w/
5.
▲
by
LoadingALIAS
4mo ago
Okay, I finally have a second to breathe. Sorry for the delayed response - life and all that. I am not claiming the entire crate is constant-time, and if the README reads that way, that is my mistake. My intended claim is MUCH narrower... s
6.
▲
by
LoadingALIAS
4mo ago
Hey! Thank you for taking a second. Really, I appreciate it. So... fair criticism. The constant-time line is too compressed and should probably be replaced w/ some kind of matrix. I ask you to give me a few hours. I'm not able to
7.
▲
by
LoadingALIAS
4mo ago
The documentation and to a large extent commenting, auditing, and almost every markdown file was likely generated with an LLM. Do not mistake that for competence or quality. This is a pre-v1 codebase. I'm looking for bench-methodology
8.
▲
by
LoadingALIAS
4mo ago
Yeah, all fair questions. To address the LLM question - almost all MD files in the codebase were built around the codebase by an LLM. I simply don't have the time; this project is a side project and not my main squeeze. This is also a
9.
▲
by
LoadingALIAS
4mo ago
I've built rscrypto because crypto kept being where my Rust database stopped being portable: different stack on the server, different target story on WASM, different answer on RISC-V/POWER/IBM Z, and a different audit surface
10.
▲
Show HN: Rscrypto, pure-Rust crypto with industry leading public benches
(github.com)
33 points
by
LoadingALIAS
4mo ago
|
15 comments
11.
▲
by
LoadingALIAS
9mo ago
Honestly, I'd targeted 10... but I wasn't going to weaken the binary for an arbitrary number.
12.
▲
by
LoadingALIAS
9mo ago
I owe the OSS community; I'm trying to pay you all back. Haha.
13.
▲
by
LoadingALIAS
9mo ago
You're welcome. I hope it's helpful!
14.
▲
by
LoadingALIAS
9mo ago
Hey. Author here. I wrote a longer post about the motivation and design: https://dev.to/loadingalias/cargo-rail-making-rust-monorepos... The Problem: I've been working on a low-level Rust workspace for a while now
15.
▲
Show HN: Cargo-rail: graph-aware monorepo tooling for Rust; 11 deps
(github.com)
61 points
by
LoadingALIAS
9mo ago
|
7 comments