Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
briansmith
searching Neon…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
5 ms
·
1.
▲
by
briansmith
1mo ago
Are they the authors of the “informal note” or not? I’ve never seen a math paper of any formality written without the authors’ names on it before.
2.
▲
by
briansmith
1mo ago
> Two mathematicians at Anthropic studied and validated Claude’s paper, and produced an informal note for experts stating Claude’s proof concisely. Why hide the names of the people who wrote the second paper? To discourage people from ci
3.
▲
by
briansmith
3mo ago
If differential parsing of X.509 certificates is a material security concern for something, then that's a bug in that thing.
4.
▲
by
briansmith
3mo ago
Just to be clear, OpenSSL isn't doing the wrong thing, based on the description in the blog post. The specification allows and even requires behavior similar to that.
5.
▲
by
briansmith
3mo ago
This is uninteresting. CAs are well aware that they have to encode the subject DN and issuer DN identically to maximize interoperability. There are several implementations that require that. If we were to make a new version of the spec for
6.
▲
by
briansmith
5mo ago
Pretty much all the routers that are targeted by the ban would be OpenWrt derivatives, AFAICT. It’s basically the Android of routers, except without the Google resources. Google Wifi Is one of the main lines that aren’t based on OpenWrt. I
7.
▲
by
briansmith
5mo ago
> We have been assessing our existing processes (for OpenWrt, and especially the OpenWrt One) against NIST IR 8425A, and are now accelerating those efforts to ensure we can show that routers using OpenWrt are indeed safe and secure, as d
8.
▲
by
briansmith
5mo ago
[I was at Mozilla during the development of BrowserID but I didn’t work directly on it. I was a huge fan of the effort.] Besides non-obvious UI issues, there were fundamental issues. One in particular that was very hard to overcome: Very fe
9.
▲
by
briansmith
5mo ago
The purpose of a system is what it does.
10.
▲
by
briansmith
5mo ago
Many implementations limit the RSA key size to 8,192 or 16,384 bits (because the maximum bit length determines indirectly how much stack space is required).
11.
▲
by
briansmith
7mo ago
BenQ PD2730S.
12.
▲
by
briansmith
1y ago
Actions have special integration with GitHub (e.g. they can annotate the pull request review UI) using an API. If you forgo that integration, then you can absolutely use GitHub Actions like "a container you run scripts in." This i
13.
▲
by
briansmith
2y ago
At https://rwc.iacr.org/2025/program.php you can see there is a talk scheduled to be given in a couple weeks titled "Testing Side-channel Security of Cryptographic Implementations against Future Microarchitectures
14.
▲
by
briansmith
2y ago
Which CA's will issue short-lived certificates without negotiating a custom ($$$) contract with them?
15.
▲
by
briansmith
3y ago
Again, this is just a temporary situation, and a matter of burning down a list of small tasks. Not that the OpenSSL license issue is a big deal for most anyway. Feel free to help; see this issue filed by Josh Triplett: https://gi
16.
▲
by
briansmith
3y ago
> Maybe so, but pretty much all cryptographic primitives have to be written in assembly anyway to achieve constant time operation. This really oversimplifies the situation. Even at my most pessimistic, I believe just a very few, very sma
17.
▲
by
briansmith
3y ago
I think that's a really good question. The way this worked out is worth studying in detail. What was the process with which the AES-GCM cipher suites for SSH were developed? What was the process with which the ChaCha20-Poly1305 cipher
18.
▲
by
briansmith
3y ago
> But it took until 2023 for someone to do the legwork to figure out how broken it was. It took until 2023 for somebody to publicly disclose the problem. The first fix for it was described in RFC 5647, which was published in August 2009
19.
▲
by
briansmith
3y ago
There are multiple reasons for a user to want "dark mode": * I just want everything to be dark on my screen because I like it. * I am trying to use this device in a dark place. * I want a dark, low-contrast background that doesn&#
20.
▲
by
briansmith
4y ago
The the old yanking policy was extra work I did with the intent to help people. It was unfortunate that Cargo had that bug, but also I should have been much more diplomatic in how I dealt with it. I've just returned from a long break a
21.
▲
by
briansmith
5y ago
> Bundling this set with Firefox I love that they did that; it was actually my idea ( https://bugzilla.mozilla.org/show_bug.cgi?id=657228 ). I believe the list is pretty large and changes frequently and so they download it
22.
▲
by
briansmith
5y ago
Are you assuming that the set of certificates that is given as input is the complete search space? It isn't; the server might have failed to send some certificate that, if present, would have fixed the "unknown issuer" proble
23.
▲
by
briansmith
5y ago
In a properly-designed CI/CD system, a dependency getting yanked isn't an emergency unless you choose to treat it as such. In particular, if you don't want your build to fail because some dependency got yanked then you need t
24.
▲
by
briansmith
5y ago
> he situation described above just generated an "Invalid certificate" message. More use of anyhow::Context would be helpful. I don't disagree with Rustls disallowing decade-obsolete crypto. It's the "silently ig
25.
▲
by
briansmith
5y ago
> The EverCrypt primitives are formally proven, whereas ring has no such formal proofs. We do use some of the Fiat Crypto stuff for elliptic curve computations. I am not opposed to switching some stuff to use EverCrypt or other things th
26.
▲
by
briansmith
5y ago
The goal of the ring project is to be much safer than OpenSSL without any notable decrease in performance. That is, my goal is to give you memory safety "for free" if you switch from OpenSSL/BoringSSL to ring . In some cas
27.
▲
by
briansmith
5y ago
When I merged security fixes from BoringSSL/OpenSSL, I yanked the old versions of ring that didn't have the security fixes. I thought that was a pretty reasonable policy, however people who like to comment in these forums disagr
28.
▲
by
briansmith
5y ago
That hasn't been the case for a long time, a year or more.
29.
▲
by
briansmith
6y ago
There are lots of people doing awesome stuff with cryptography in Rust, including (but not limited to) the people who maintain Mundane. You are right that ring has a much-reduced set of build dependencies compared to Mundane/BoringSS
30.
▲
by
briansmith
6y ago
There isn't yet any name mangling in the C/assembly function names that would prevent collisions between two incompatible versions. I use `links = "ring-asm"` in Cargo.toml to prevent people from accidentally including t
More ›