dzdt
Joined 12 years ago
Karma
8,233
Submissions
1,140
Member since
Aug 8
Recent submissions
Comment · 1 hour ago
Comment · 2 days ago
Article is dated (2016).
Comment · 9 days ago
And the key has no notches, and so inserting a screwdriver into the lock and turning works just as well as using the key.
Comment · 17 days ago
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.
Comment · 1 month ago
Not generally true in the United States.
Comment · 1 month ago
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!"
Comment · 1 month ago
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."
Comment · 2 months ago
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...
Comment · 2 months ago
There are a lot of cars out there where the head unit has connection to the CAN bus. Which means this malware vector could be used to directly cause crashes. E.g. https://news.ycombinator.com/item?id=19751872
Comment · 2 months ago
What is an "OG image"?
Comment · 2 months ago
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)?
Comment · 2 months ago
If you are healthy and kid free, you can just not go to the doctor.
Comment · 2 months ago
Better article with good pictures : https://thursd.com/articles/helio-da-silva-sao-paulo-tiquati...
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.