insanitybit

Well I'm not a random HNer lol I work in security.

Are you suggesting that they've come up with a novel technique that doesn't involve sharing a CPU core? I'm open to that.

From what I can tell, this is not the case, but I haven't read a detailed report (I don't know of one, would be cool if it's out there though).

> something that our systems are meant to prevent

What prevention method did they take? Like, did they run with hyperthreading enabled or something by accident?

Did they discover a new cache timing technique or is this just the standard stuff?

If they just had hyperthreading on maybe they need to hire someone who knows more about this stuff.

Two VMs should never be sharing a physical core. If they don't know this, yikes.

uv defaults to its own trust store afaik lol

The vast majority of web services are not written in memory unsafe languages so this is not surprising.

One of the exceptions (with regards to web facing attack surface in a memory unsafe language) is that people still use OpenSSL, which has a terrible history of memory unsafety, including the cited heartbleed.

It was.

I don't care, nor should anyone else

Sure, I think it was still under the same unsound tag regardless.

I don't think the definition of "memory safe" has ever required full end to end stack conformance with a proof. Very few languages have achieved that, though some have. Most people call Java memory safe, C#, Python, Typescript, etc - all of those fall short of a formally verified, sound type system with a verified toolchain.

lol I was writing `l` because I thought it was `labeled-unsound` for like a fucking decade

For a long time `loop {}` was undefined behavior. Lots of l-unsounds are really nuts but a few are not.

The reality is that if this were actually code that people wrote, well, it wouldn't have sat around for a decade.

lol do you think that cve-rs was required? there is literally an l-unsound tag on rustc's github, this isn't some embarrassing or secret thing.

Safe rust is safe, granting `unsafe` and compiler errors. This isn't a secret.

This doesn't work when every candidate holds the same position.

I mostly use Haiku for really, really basic stuff, never for actual engaging work. I've used it for first-pass analysis to triage bugs, for example - all it does is related N bugs together to see if any potentially relate. Then I have Sonnet investigate further.

No. It's because Greg doesn't like the CVE system and MITRE, the stupidest decision ever, made Greg a CNA, and this is his tantrum that he's been waiting 40 years to throw.

I think the current state of bug bounties demonstrates that it's about the eyes, not the number.