kingkilr

7 ms·

1.
by kingkilr 7mo ago
[Work at Anthropic, used to work at Mozilla.] Firefox has never required a full chain exploit in order to consider something a vulnerability. A large proportion of disclosed Firefox vulnerabilities are vulnerabilities in the sandboxed proce
2.
by kingkilr 1y ago
(pyca/cryptography dev here) As Steve notes, Rust does support s390x. Even prior to shipping Rust code, we never tested or claimed to support s390x. If there's genuine interest in more people supporting s390x in the open source wo
3.
by kingkilr 2y ago
RealPage was DoJ. As was the Google search litigation where DoJ proposed Google divest Chrome. Which is by way of saying, the FTC and Chair Khan were not responsible for those.
4.
by kingkilr 2y ago
I would strongly implore people not to follow the example this post suggests, and write code that relies on this monotonicity. The reason for this is simple: the documentation doesn't promise this property. Moreover, even if it did, th
5.
Measuring and Improving Rustls's Multithreaded Performance(rustls.dev)
5 points by kingkilr 2y ago|0 comments
6.
Passing nothing is surprisingly difficult(davidben.net)
180 points by kingkilr 3y ago|70 comments
7.
by kingkilr 4y ago
Since last year's AMG case in the Supreme Court, the FTC is not authorized to seek monetary relief in these cases. The FTC can seek monetary relief if this order is violated.
8.
by kingkilr 5y ago
I don't know Brett super well so I can't speak to the rest of his background, but it's not correct that the Obama admin asked him to take over DDS. DDS's founding head was Chris Lynch, who served in that role until the m
9.
by kingkilr 6y ago
While I don't love the proliferation of dependencies, from a risk perspective the raw number of dependencies isn't always the right metric. Looking at the authors and publishers numbers from https://github.com/rust
10.
by kingkilr 6y ago
I think it's fair to say that this work is quite likely to qualify :-)
11.
by kingkilr 6y ago
Rust has a few interlocking behaviors that provide its memory safety, a few of the most important are: - The borrow checker enforces mutable XOR shared references. - The compiler does not allow use of local variables before they're ass
12.
by kingkilr 6y ago
Sure you can. First, in a philosophical sense: pointers and x86 CPUs are real, ultimately any safe abstraction must be built on unsafe primitives. The ability and need to do that aren't specific to memory unsafety, we do that all over
13.
by kingkilr 6y ago
I don't have any data on exploitability, but 19 of the last 22 vulnerabilities (since 2018) have C-induced memory unsafety as a cause: https://curl.haxx.se/docs/security.html
14.
Memory safe ‘curl’ for a more secure internet(daniel.haxx.se)
407 points by kingkilr 6y ago|204 comments
15.
by kingkilr 6y ago
It's a great question! a) It being acceptable to upstream is mandatory to receive a bounty, so a starting point might be: pick projects whose maintainers are sick of dealing with ASAN reports! b) A huge number of people get their libpn
16.
by kingkilr 6y ago
Lots of drivers, network protocols, etc. in the kernel, and they're most of the attack surface -- not the scheduler :-) We have to approach this as a question of how, not if. When we do that, we can change computer security.
17.
by kingkilr 6y ago
The kernel maintainers have actively expressed interest in having upstream support for writing kernel modules in Rust!
18.
by kingkilr 6y ago
Those of us who organized this both have a long history of involvement in open source. If we have even an iota of this becoming a problem, we will a) be incredibly saddened, b) figure out how to restructure the rules to address the behavior
19.
by kingkilr 6y ago
One of the folks behind the bounty here. Happy to answer questions.
20.
Fish in a Barrel NSA Inspired Memory Unsafety Posters(langui.sh)
6 points by kingkilr 6y ago|0 comments
21.
by kingkilr 7y ago
(Former Firefox Security Engineer) I suspect it's because Firefox exploits have looked the same for the last several years -- there has not been a lot of novelty required to implement an exploit, given an arbitrary read/write prim
22.
by kingkilr 7y ago
As far as we know the entire kernel for both is memory unsafe. It's not clear to me how much Swift is in use internally for things besides apps (e.g. is there a future where Window Server is Swift?)
23.
Notes on the challenges to the adoption of security keys(alexgaynor.net)
2 points by kingkilr 7y ago|0 comments
24.
by kingkilr 7y ago
29/51 appear to be memory unsafety https://twitter.com/LazyFishBarrel/status/111032101282489958...
25.
The Internet Has a Huge C/C++ Problem and Developers Don't Want to Deal with It(motherboard.vice.com)
7 points by kingkilr 8y ago|0 comments
26.
by kingkilr 9y ago
This release has our continued progress on sandboxing.
27.
by kingkilr 10y ago
It's not in this post, but this will only apply to publicly trusted roots, not "enterprise" ones.
28.
by kingkilr 10y ago
Happy Birthday Pandoc! The ability to write and collaborate on memos in markdown, and turn them into fancy PDFs and .docs is seriously world changing.
29.
by kingkilr 10y ago
Hi! Engineer at USDS here. There's definitely quite a bit of PostgreSQL in use in government, so this does not need to be a blocker. As someone noted, PAM auth is a good solution; and I think if you use CentOS or RHEL (Use the latest r
30.
by kingkilr 11y ago
David's the best :-)

More ›