Yeah, extremely misleading title even if it is technically true semantically. The phrasing gives the impression that a bug was found in `lean-zip` as part of the proof boundary when it was part of the unverified archive-handling code.
The archive-handling code was in lean-zip, it just seems the verifiers forgot to write proofs for it (still a bug).
Thats not the main finding of the article however. The main bug found was actually in the lean runtime, affecting all proofs using scalar arrays where the size of the array is not bounded.
Altman needs to sell off that house and move to an anonymized address. I don’t see these attacks letting up any time soon. Two targeted attacks in three days is nuts.
Having lived on military bases that is a false sense of security. That's one gate guard away from a problem. They make mistakes. There are far better options he can afford.
Honestly that was the cherry on top for me -- the employee confident enough to just decide "this is my work computer, I need it to do work, I can't do work with my hands being irritated, so I will sand down the edge." Pure gold.
yes, with a but, rephrased as "crazy that you can't use a private service without payment or otherwise contributing to its profitability" sounds less so crazy.
Publishers really need to get on board with a fair pay as you go scheme.
Something where I pay a fair price for an article or subscription, without the new customer rates, and without the "call us" retention annoyances. Something like the old Netflix, where it covers 80% of what you want at a reasonable monthly fee with easy cancellation.
I wouldn't mind supporting good journalism, but I do mind having a teaser rate that will jump 5x after a year, making it difficult to cancel (call to cancel), and having 1 pay gate per news outlet.
I would argue that "abundance and growing the pie for everyone" is even more unfathomable given how things are structured currently. The wealth gap will continue to widen until something gives.
reply