HN Simulatornew | past | comments | lists | submit | amstan's commentslogin

When I was a kid and read 800 Leagues I proceeded to make a whole encryption IDE in Visual Basic 6 for a programming fair that year. I called it "Crypt+". It even had C++ dll based encryption engine plugins.

The funny thing is that I got that book as a prize from a previous year's programming fair.


Nice.

However, I was a kid in the seventies, when PCs were still in the future, so I had to practice cryptography with pen and paper.

While in high school, I wrote my first programs, but at that time this was done by writing the program (e.g. in FORTRAN) on a special printed form, on a grid where each character was accurately positioned, then the form was given to an operator who transferred the written program on 80-column punched cards, and then the next day you could retrieve the printed results from running your program on an IBM mainframe (printed with a 132-column line printer), together with the deck of punched cards, to be used if you wanted to rerun the program (which you almost always wanted to do, even if the program had been intended to be run only once, because your first attempt of running might have printed only compiler error messages).

There has been a long journey from that until being able to use VB6 or Visual C++.


Reminds me of the Xfinity "Your personalized WiFi summary" emails. Despite returning their router, using a third party almost-layer-2 modem, my own openwrt router (with its own wifi, thank you very much), their emails seem spooky.

They have a counter of all of my devices, somehow (i mean... i guess their count is wrong, but it's infuriating that they try to keep track).


All of that could be done without "ISP was hijacking my DNS". DPI/SNI sniffing is more accurate and allows you to get more detailed statistics (eg. "20% of your bandwidth goes to youtube"


I can't tell if any of this gives you more access than the normal http admin interface.


As far as I can tell, it doesn't. The web interface is like 90s website but it does have a million suboptions. None of these seem like it needed any hacking. I am not sure about the Debug ones. I'll have to check. I wouldn't be surprised if there was an available api listening with the same commands available. If not that would be the useful outcome from work like this. A CLI that implements these.

Now if you could use to allow firmware downgrades when the installed firmware doesn't, that would be useful too. I disabled updates on mine at a version that already allows it. I bought it a few weeks ago but luckily it didn't come with the latest "I don't like your ink chip" firmware.


Well now you can point an LLM at it. I’m not sure that gives you anything either, but I’m not sure the hacker ethos makes that a priority.

Sometimes a hack is just cool because it’s a hack.


On the other hand, my local qwen model (3.8-flash-next) was trying to convince me that the eMudhra CA thing is no big deal since you need to be "positioned correctly" (eg: any wifi network) to be able to MITM, and most of the IOT devices would have patched stuff by now.


The CA thing is bad, but in practice a lot more high effort to exploit. As a prerequisite the attacker has to be present on the same network, which makes any individual attack a lot more high effort. In contrast for something like PHP2Shell (if exploitable) any PHP instance exposed on the internet can be attacked by anyone from anywhere.

With a MITM, you also mainly breach confidentiality, but this doesn't directly give you an exploit chain to pwn the device (though the many auto-updaters people are using nowadays might be one).

For IOT devices, there are also factors that limit the exposure. The certs are only from 2025/2026, so few devices with them installed are likely present in any given home, and depending on the hardware footprint devices may only come with the few select CAs bundled that they require due to size constraints anyways.


Anyone in the connection chain can easily exploit the CA leak. Easiest example is your ISP.


Yeah, it's going to be hard for someone to pick an arbitrary target and get into a position to exploit it, but there are an enormous number of people who are in the position to exploit someone.

One rogue employee at Cloudflare could MITM half the Internet if they are able to get around whatever internal safeguards exist.


Ah yes, IoT devices, known for their rock solid security


sounds like you quantized it a bit too hard


Just to close the loop, AXI bus[1] refers to a very common implementation, in the gateware/verilog, of a MIMO.

[1] https://en.wikipedia.org/wiki/Advanced_eXtensible_Interface


> Framework chose to not provide a header for flashing the BIOS, which, when combined with issue #3, forced the use of pogo pins.

Op probably missed https://github.com/FrameworkComputer/FrameworkDebugger#jspi. Though, the connector is not populated for cost reasons.

Otherwise, I agree with the author, this is a pain.


Original author here:

Thanks for linking the documentation! To be clear, when I wrote "header", I meant something with a connector that can be easily used for this purpose. Soldering on the connector is probably more difficult than the pogo pins that I used.

I also can't help but notice the linked connector is less than $1 in bulk on DigiKey and probably cheaper if ordered at Framework's scale.


Sure, but this is just one issue. How many potential $0.78 connectors exist? If one in 1000 customers has a need for a connector, and there are 40 different potential failure modes where a $0.78 connector would make recovery easier, is that worth the extra $30 per laptop?


I checked the pictures of my board, and there are 3 unpopulated headers that I can see. There's also the unpopulated BIOS chip socket, which is similarly cheap. I think I would pay the extra $3 per laptop for better repairability, which is Framework's entire sales pitch anyway.


Moving to sockets adds risk of the socket failing too. But this particular instance of not using an SOIC-8, for which test clips are readily available, seems pretty unfriendly.

I imagine there's a way to program the flash from a header or connector, or maybe it was programmed before being assembled onto the PCB.


Having a BIOS update BRICK the device isnt 'just one issue', they clearly need to do more work to protect devices from this, they can choose what they add but the BIOS needs a safer fallback and recovery process, that much is clear.

Definitley worthy of even an extra $1-2 per laptop if needed.


The user is not guilty of "missing" this if fw never pointed to it when asked directly.

And where is the bios image to use with this anyway? Including the documentation to fix the serial numbers.

The existence of this header changes exactly nothing about the story.


Accessing a GPU bar via USB2&3 endpoints seems novel.

[1] https://github.com/tinygrad/asm2464pd-firmware/blob/master/U...



related, now-classic SNL skit linked in the article: https://www.youtube.com/watch?v=jVhlJNJopOQ


It is such a classic, it got a sequel - https://www.youtube.com/watch?v=Q8PdffUfoF0


Guidelines | FAQ | Lists | API | Security | DMCA | Apply to YC | Contact

Search: