dochtman

16 ms·

181.
Aya: writing eBPF in pure Rust(confused.ai)
5 points by dochtman 5y ago|0 comments
182.
by dochtman 5y ago
Do you think Seveneves is weaker than Fall? That seems like a really hard sell to me.
183.
by dochtman 5y ago
https://dirkjan.ochtman.nl/writing/2018/07/15/science-fictio...
184.
by dochtman 5y ago
I think I’ve noticed that cargo install would pick up newer semver-compatible versions than what was in the lockfile unless I passed —-locked explicitly, which seemed surprising to me.
185.
by dochtman 5y ago
I have a fair bit of experience writing Rust code and the current status is totally deliberate. I find module file sizes of about 400-800 lines of code optimal in terms of my ability to find things vs the unnecessary complexity of having to
186.
by dochtman 5y ago
If you look at the chart in this article, it looks like energy density has been on a linear rather than exponential path for the last three decades.
187.
by dochtman 5y ago
Working from home.
188.
by dochtman 5y ago
I use Secretive to authenticate to SSH (including GitHub) with my Mac’s TouchID. Feels like this is (almost) as secure, while being more convenient (no extra hardware required). Of course it is a Mac-only solution.
189.
by dochtman 5y ago
QUIC does run in user space, and also uses congestion controllers running inside the QUIC stack, in user space. (I work on a QUIC implementation in Rust.)
190.
by dochtman 5y ago
I don't know your context, but here are some thoughts on what I've seen/experienced: Allow remote work -- European rates are much lower than Silicon Valley rates even now, and I imagine the same might be true for other parts
191.
by dochtman 5y ago
Is there documentations of the protocols used for this?
192.
by dochtman 5y ago
If you reply here, I'm happy to relay your comments to that issue.
193.
by dochtman 5y ago
I don't think the list of possible future features has been kept especially up-to-date -- we should probably fix that (or get rid of the list). If you want to weigh in on that issue to discuss why you think it's a valuable feature
194.
by dochtman 5y ago
On the Python angle, I recently spent some time building Python bindings for another Rust project with PyO3 and was quite happy with the result. Since then, I’ve been toying with the idea about building a somewhat compatible replacement for
195.
by dochtman 5y ago
See my other answer.
196.
by dochtman 5y ago
That issue should be fixed in the next release. It is definitely a nuisance, but fixing it is not easy due to the assembly code involved.
197.
by dochtman 5y ago
It uses ring for cryptographic operations, yes. However, note that all the ASM in ring is meticulously kept up to date with BoringSSL upstream, which ring was derived from. Plus, there was pretty successful third-party security audit last y
198.
by dochtman 5y ago
Happy to answer any questions that come up!
199.
by dochtman 5y ago
This is actually not (2018), it’s from a few days ago.
200.
by dochtman 5y ago
The list of unstable features they want to use is interesting: https://github.com/Rust-for-Linux/linux/issues/2
201.
by dochtman 5y ago
The list of unstable features they want to use is interesting: https://github.com/Rust-for-Linux/linux/issues/2
202.
Surprisingly Slow(gregoryszorc.com)
559 points by dochtman 6y ago|148 comments
203.
by dochtman 6y ago
The API has generally been pretty stable, so I don't think you should be too worried about that. I haven't talked to other stakeholders about a version 1.0, and we actually have some larger API changes cooking right now. For now w
204.
by dochtman 6y ago
I think ring does support WebAssembly. Yeah, the ASM in ring is not great, but unfortunately Rust does not currently provide us with all the guarantees we need to write safe crypto code (for example, timing guarantees). We hope this wil
205.
by dochtman 6y ago
We have some documentation on what we've done to learn from previous vulnerabilities: https://docs.rs/rustls/0.19.0/rustls/manual/index.html We try very hard to model our code as a constrained state
206.
by dochtman 6y ago
Match statement exhaustiveness checking is one example, especially combined with the pervasiveness of enums (instead of constants).
207.
by dochtman 6y ago
No argument from me that you can easily go wrong in any language, but I would argue that Rust has features other than memory safety that can also assist in building more reliable/secure software.
208.
by dochtman 6y ago
I am a maintainer for rustls ( https://github.com/ctz/rustls ). What would your team need to be able to migrate to a different TLS stack that so far has proven to be safer, and passed its first security audit with flying
209.
by dochtman 6y ago
Actually, the effort that started towards this blog post started weeks ago, easily several weeks before the blog post you're referencing.
210.
by dochtman 6y ago
What's especially annoying is that most PRs seem to get a green checkmark for me as if checks have passed, when tests actually just haven't been started. It seems like it ought to be possible to do better than this. Right now the

More ›