dzdt
dzdt on Hacker News
The forensic report on the failure of the cable sockets is at
https://www.thorntontomasetti.com/sites/default/files/2022-0.... Unlike the linked article this includes detailed diagrams and discussion explaining how these sockets worked and how they failed.
My attempt at a quick summary: the Arecibo instruments were held up by heavy steel cables, which are composed of a bundle of 126 to 216 individual wire strands twisted together, where each wire strand is about 1/4 inch diameter. At the cable ends these were anchored in sockets. The socket is conical, widening out towards where the wire ends go. The wire strands of the cable would be separated in a "broom" shape to fill out that conical area, and then the whole thing filled in with molten zinc.
The failure mode of these zinc-filled sockets is for an inner core cylinder, about the same diameter as the cable body, to pull out from the socket while outer strands of the cable which are broomed out of that core either snap or pull free from the zinc plug.
This failure mode hadn't really been seen prior to the Arecibo collapse, partly because it is a long term process where the zinc slowly flows under stress over decades.
And the key has no notches, and so inserting a screwdriver into the lock and turning works just as well as using the key.
I am less interested in the threat models than the accidental denial of service models. I've avoided passkeys because of that. It seems like there are real problems if you use multiple devices not somehow symced.
Not generally true in the United States.
This article seems to be completely based on the X post by the reverse engineer DiscoStarSlayer :
https://x.com/DiscoStarslayer/status/2099132300390744320.
That post reads "After 4 years of effort, I'm happy to announce that one of the final secrets of the PS2 has been broken wide open!
It's been a long process of decapping, optical dumping, and now at last a software solution.
Thank you Libby for finding the exploit from our dirty optical dumps!"
Yesterday DiscoStarSlayer also promised details are coming: "Will share full write-up on how we got here soon!"
Matt Pharr (author of the SIMD programming language ISPC) nailed it with the insight "Auto-vectorization is not a programming model."
As Matt writes ([1]) : "
The problem with an auto-vectorizer is that as long as vectorization can fail (and it will), then if you’re a programmer who actually cares about what code the compiler generates for your program, you must come to deeply understand the auto-vectorizer. Then, when it fails to vectorize code you want to be vectorized, you can either poke it in the right ways or change your program in the right ways so that it works for you again. This is a horrible way to program; it’s all alchemy and guesswork and you need to become deeply specialized about the nuances of a single compiler’s implementation—something you wouldn’t otherwise need to care about one bit."
[1] https://pharr.org/matt/blog/2018/04/18/ispc-origins
Was daydreaming the other day about how this could be used by adversaries to hack even air-gapped computers. Any peripheral which contains a microchip and some ram is a vector. Does the compartmentalized facility ever bring in a new monitor, or mouse, or keyboard? All of those things could be hacked to hack their new host. And then taking data into/out of the facility. Which devices have lights? Any LED that can be blinked is a low-speed output channel. Which have light-level sensors, or sound sensors? Or any RF capability? If bluetooth is disabled by software but the hardware is still there...
If I was writing a novel, the top secret facility would be cracked open by the smoke alarm, which has a wired connection to the central fire control and runs a little microprocessor. There is enough storage for 20 programmable voice alert messages. I/O includes an LED and also a light sensor. After the attacker gains control of the smoke alarms -- reach to every room of the secure facility -- their focus turns to mass poisoning peripherals until one makes it into range. A poisoned monitor detects the smoke alarm blinking a coded broadcast via its LED during darkened overnight hours. The monitor responds with flashing code of its own. That creates a communication path back to the controlling LLM. From there its like attacking a normal networked device, just with a slow data link in the middle...
So on an affected system, ring 0 root has access to pretty much everything that was hidden in negative ring territory. The page is pretty quiet about what other processor families might be similar beyond this specific AMD16h (an older AMD low-power family)?
If you are healthy and kid free, you can just not go to the doctor.
Posted by
dzdt on Wednesday August 05, 2026 @07:03AM
from the wired.com dept.
Make it a tinfoil hat :-)
I think you are right on the big picture : what has changed is Big Tech has recognized that comprehensive data on individuals is valuable. I think the biggest value category however is in the area of highly-targeted opinion manipulation. Build a model of what are the current beliefs of each individual, get paid by marketing or political candidates or whoever to generate an optimized media feed to manipulate that person's beliefs to match some target set of beliefs.
Posted by
dzdt on Wednesday May 20, 2026 @06:44AM
from the mpaldridge.github.io dept.
It seems like Barron only ever managed to flash 14 beanbags that one time in 2017 and neither he nor anyone else has repeated or exceeded that since.
Yes trying to read that article my brain refused to parse "EviCore" as anything but "EvilCorp". Every time.
I think the new model with music is they don't make a very serious attempt to keep a monopoly on the content. They only really care about a monopoly on convenience. If anyone would set up some convenient way to stream these concert recordings they would get sued to oblivion. But the recordings circulating as inconvenient downloads? Not a big target.
At least in the early 2000s, Bloomberg had strict requirements about this. Their financial terminal has a ton of math calculations. The requirement was that they always had live servers running with two different hardware platforms with different operating systems and different CPU architectures and different build chains. The math had to agree to the same bitwise results. They had to turn off almost all compiler optimisations to achieve this, and you had to handle lots of corner cases in code: can't trust NaN or Infinity or underflow to be portable.
They could transparently load balance a user from one different backend platform to the other with zero visible difference to the user.
Guessing not knowledge but I expect it was called that from the accidental occurence of color on broadcast TV wben the image includes something with black-and-white stripes at the right spacing. So the name predates the intentional usage by the comphter system.
I think in this alternate universe the Apple-II analog would be the first cheap computer that could run a spreadsheet. That really takes a 40 column display. So I think it would have waited for the 2mhz 6502 to handle the doubled line frequency.
I do think there is a strong possibility the people in charge in the US government believe an Iran state sponsored terrorism attack would be a political benefit to them. Such things boost support for the sitting President, and could also give political cover for additional authoritarian acts to help them retain power. Would they do the school attack on purpose? Maybe? But for sure they keep the war going until they generate the response they are looking for...
Is this something European style privacy laws would protect against? Though given the US political situation we are far from being able to enact any kind of anti-authoritarian protections...
I think it could be solved still pseudononymously: introduce a "vouch" button that allows a user to vouch that another user is human. This is consequential both for the vouched-for and vouching accounts. Run a page-rank style algorithm on the graph of vouches to generate a certainty score for the humanity of each account. For repeated posters this should converge to a correct answer fairly quickly. There is still a challenge for green accounts, but having degraded experience for new users is not a doom scenario for the site.
For purely historical reasons the C/C++ stack is "small" with exactly how small being outside of programmer control. So you have to avoid using the stack even if it would be the better solution. Otherwise you risk your program crashing/failing with stack overflow errors.