frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

OpenCiv3: Open-source, cross-platform reimagining of Civilization III

https://openciv3.org/
487•klaussilveira•7h ago•130 comments

The Waymo World Model

https://waymo.com/blog/2026/02/the-waymo-world-model-a-new-frontier-for-autonomous-driving-simula...
828•xnx•13h ago•495 comments

How we made geo joins 400× faster with H3 indexes

https://floedb.ai/blog/how-we-made-geo-joins-400-faster-with-h3-indexes
48•matheusalmeida•1d ago•5 comments

Show HN: Look Ma, No Linux: Shell, App Installer, Vi, Cc on ESP32-S3 / BreezyBox

https://github.com/valdanylchuk/breezydemo
163•isitcontent•8h ago•18 comments

A century of hair samples proves leaded gas ban worked

https://arstechnica.com/science/2026/02/a-century-of-hair-samples-proves-leaded-gas-ban-worked/
104•jnord•4d ago•15 comments

Monty: A minimal, secure Python interpreter written in Rust for use by AI

https://github.com/pydantic/monty
159•dmpetrov•8h ago•74 comments

Dark Alley Mathematics

https://blog.szczepan.org/blog/three-points/
57•quibono•4d ago•10 comments

Show HN: I spent 4 years building a UI design tool with only the features I use

https://vecti.com
267•vecti•10h ago•127 comments

Microsoft open-sources LiteBox, a security-focused library OS

https://github.com/microsoft/litebox
334•aktau•14h ago•161 comments

Show HN: If you lose your memory, how to regain access to your computer?

https://eljojo.github.io/rememory/
216•eljojo•10h ago•136 comments

Sheldon Brown's Bicycle Technical Info

https://www.sheldonbrown.com/
329•ostacke•13h ago•87 comments

PC Floppy Copy Protection: Vault Prolok

https://martypc.blogspot.com/2024/09/pc-floppy-copy-protection-vault-prolok.html
31•kmm•4d ago•1 comments

Hackers (1995) Animated Experience

https://hackers-1995.vercel.app/
418•todsacerdoti•15h ago•220 comments

Show HN: ARM64 Android Dev Kit

https://github.com/denuoweb/ARM64-ADK
9•denuoweb•1d ago•0 comments

Delimited Continuations vs. Lwt for Threads

https://mirageos.org/blog/delimcc-vs-lwt
8•romes•4d ago•1 comments

An Update on Heroku

https://www.heroku.com/blog/an-update-on-heroku/
349•lstoll•14h ago•245 comments

Show HN: R3forth, a ColorForth-inspired language with a tiny VM

https://github.com/phreda4/r3
55•phreda4•7h ago•9 comments

How to effectively write quality code with AI

https://heidenstedt.org/posts/2026/how-to-effectively-write-quality-code-with-ai/
205•i5heu•10h ago•150 comments

I spent 5 years in DevOps – Solutions engineering gave me what I was missing

https://infisical.com/blog/devops-to-solutions-engineering
117•vmatsiiako•12h ago•43 comments

Learning from context is harder than we thought

https://hy.tencent.com/research/100025?langVersion=en
155•limoce•3d ago•79 comments

Introducing the Developer Knowledge API and MCP Server

https://developers.googleblog.com/introducing-the-developer-knowledge-api-and-mcp-server/
30•gfortaine•5h ago•4 comments

Female Asian Elephant Calf Born at the Smithsonian National Zoo

https://www.si.edu/newsdesk/releases/female-asian-elephant-calf-born-smithsonians-national-zoo-an...
12•gmays•3h ago•2 comments

Understanding Neural Network, Visually

https://visualrambling.space/neural-network/
254•surprisetalk•3d ago•32 comments

I now assume that all ads on Apple news are scams

https://kirkville.com/i-now-assume-that-all-ads-on-apple-news-are-scams/
1008•cdrnsf•17h ago•421 comments

FORTH? Really!?

https://rescrv.net/w/2026/02/06/associative
50•rescrv•15h ago•17 comments

I'm going to cure my girlfriend's brain tumor

https://andrewjrod.substack.com/p/im-going-to-cure-my-girlfriends-brain
83•ray__•4h ago•40 comments

Evaluating and mitigating the growing risk of LLM-discovered 0-days

https://red.anthropic.com/2026/zero-days/
41•lebovic•1d ago•12 comments

Show HN: Smooth CLI – Token-efficient browser for AI agents

https://docs.smooth.sh/cli/overview
78•antves•1d ago•59 comments

How virtual textures work

https://www.shlom.dev/articles/how-virtual-textures-really-work/
32•betamark•15h ago•28 comments

Show HN: Slack CLI for Agents

https://github.com/stablyai/agent-slack
41•nwparker•1d ago•11 comments
Open in hackernews

SRAM Has No Chill: Exploiting Power Domain Separation to Steal On-Chip Secrets

https://cacm.acm.org/research-highlights/sram-has-no-chill-exploiting-power-domain-separation-to-steal-on-chip-secrets/
71•zdw•6mo ago

Comments

Gualdrapo•6mo ago
Oh, that SRAM. I once again forgot about the other SRAM and was imagining Bauke Mollema going through HN, reading this and cursing them one more time.

[0] https://www.youtube.com/watch?v=Tsk3zAZyLaQ

cycomanic•6mo ago
Ha, I was trying to parse the headline thinking about the same SRAM.
davidw•6mo ago
Or Andy Schleck https://www.youtube.com/shorts/fRWHIKE-aHM

and I'm in the same boat. Or bike, as it were, what with hours of watching the Tour this month.

NoPicklez•6mo ago
I'm pretty upset the tour has finished
motorest•6mo ago
I don't know why you are being downvoted. I also clicked on the link expecting another article on exploits being found on cycling gear. Last week I posted one about Shimano. The top comment was a joke about SRAM.

https://news.ycombinator.com/item?id=44614837

NoPicklez•6mo ago
I immediately thought it was cycling SRAM as well, thinking it was related to a post I saw once where Shimano's Di2 was vulnerable to attack
Scoundreller•6mo ago
Cool article;

Layman’s article: https://cacm.acm.org/research-highlights/technical-perspecti...

Also seems like ACM republished the author’s paper from 2022? https://dl.acm.org/doi/pdf/10.1145/3503222.3507710

My summary:

DRAM is not a safe place to store your secrets due to cold boots, so it gets stored in SRAM (which includes registers and L1/L2 cache) instead.

Buuuuut, you might be able to dump SRAM across boots with this technique.

If I understand correctly: SRAM/cache/registers all require a lower voltage to maintain their state than the cpu requires to run.

So attach that intermediate voltage on the VCC pin closest to/running the SRAM and pull the plug on everything else. I guess they’re either not cross-connected internally or the choice of voltage stops that from being a problem. Just don’t let your voltage sag lower than required to maintain the SRAM.

Now your cache/registers/SRAM are maintained. Power up with JTAG or a custom/debugging bootrom/mode that hopefully doesn’t overwrite much/any and dump away.

> Our experiments across various devices reveal that hardware SRAM resets during boot are uncommon. Most boot with undefined SRAM states, persisting until overwritten by software.

Oops.

ajb•6mo ago
Chips often have multiple VCC pins exactly because otherwise there is voltage drop across the chip. This is a hard problem. For chips where this is a security issue, I guess one answer may be to do voltage distribution on the interposer, since fewer attackers can deal with a raw die.
Scoundreller•6mo ago
If I understood the article correctly; the different on-chip elements have separate power supplies.

Makes sense: you might want to turn off the CPU but keep the SRAM/cache/etc running for hibernation, and that’s controlled externally for some reason (?)

Tuna-Fish•6mo ago
It's not normally controlled externally, but the power comes from an external source, and as the different parts of the chip want different voltages, they connect to different power sources. If you control everything outside the chip and cut the supply to parts of it, there is little that the chip can do about it, even if it normally controls distribution.
ajb•6mo ago
You're right, that was the hole here. The reply by Tuna-Fish gives the correct reason for this setup (different voltages). The actual power converter usually needs at least an off-chip capacitor, even if the logic is integrated, because that's too large to be cost-efficient in silicon; so there might be an opening even if as much as possible was integrated - haven't thought that through though.
nine_k•6mo ago
Put a pair of large MOSFETs at the power line that leads to the SRAM on the crystal; force-connect it to ground on reset or CPU power-up.
hulitu•6mo ago
> So attach that intermediate voltage on the VCC pin closest to/running the SRAM and pull the plug on everything else.

Isn't easier to just read the password from the hard drive ? You already have access.

alex-robbins•6mo ago
The use case for this is similar to the cold boot attack, e.g. disk is encrypted but memory is not. (And I don't know how encrypted DRAM works, but I wouldn't be surprised if some implementations put the key in SRAM that can be dumped using this technique.) Anyway, there may be valuable secrets that exist in SRAM but but not on disk.

https://en.wikipedia.org/wiki/Cold_boot_attack

serendipitous•6mo ago
> Now your cache/registers/SRAM are maintained. Power up with JTAG or a custom/debugging bootrom/mode that hopefully doesn’t overwrite much/any and dump away.

If you care about security, you'd be disabling these. Every product I've worked on disables JTAG and other debug features on production boards and enables secure boot.

userbinator•6mo ago
This looks like another extremely obscure attack vector which is largely leveraged only to secure devices against their rightful owners.

Physical access to these devices leads to a wide range of security exploits

Physical ownership = real ownership. That's how it's always been and should've stayed that way, if it weren't for the greedy megacorps. Valid exceptions to this level of paranoia are state secrets and other military-adjacent applications.

motorest•6mo ago
> Physical ownership = real ownership. That's how it's always been and should've stayed that way, if it weren't for the greedy megacorps.

Playing devil's advocate, what are your security expectation when someone steals your device? Is it acceptable that they immediately gain control of all services available through your them, such as email address, bank accounts, and investment portfolios?

dataflow•6mo ago
> Playing devil's advocate, what are your security expectation when someone steals your device? Is it acceptable that they immediately gain control of all services available through your them, such as email address, bank accounts, and investment portfolios?

Legally they have no right to anything. Physically, they access whatever they access. That's how it's been forever. I don't get the point of the question.

motorest•6mo ago
> Legally they have no right to anything.

What are you talking about? The scenario involves someone stealing from you. Do you think the legality of it is a dissuasion?

Also, OP's point was that "Physical ownership = real ownership."

> Physically, they access whatever they access. That's how it's been forever. I don't get the point of the question.

The whole point is that that's not the expectation or desire of every single person around you. Not one.

That's the fact you're not understanding. The ability to lock down a device and prevent unauthorized third parties from accessing it is a strong ask by everyone, not only "megacorps". The ability to track down and remotely pull a kill switch are sold as premium features by some manufacturers. Mobile operators have for a long time the ability to block cellphones by IMEI to prevent theft. A very popular product from one of the biggest companies in the world is a small tag that consumers can attack to their property to be able to find them and recover them.

And in spite of all these facts, are we suppose to pretend no one wants control access to their hardware to prevent unauthorized access from third parties?

dataflow•6mo ago
> Also, OP's point was that "Physical ownership = real ownership."

You don't have "ownership" over something you stole. You have possession of it. Possession != ownership.

> The whole point is that that's not the expectation or desire of every single person around you. Not one.

Then you're misunderstanding what people are arguing. People want the owner to be the ultimate authority. The owner gets to encrypt what they like, expose what they like, track what they like, trust megacorp they like, etc. And if a thief steals the device, they get whatever they get as a result of the owner's decisions. Which could be all their data, or a visit from the local police, depending on how the owner prepared for it.

motorest•6mo ago
> You don't have "ownership" over something you stole. You have possession of it. Possession != ownership.

You need to develop your functional literacy skills because you clearly are failing to even understand the topics being discussed, let alone the arguments going either way.

rep_lodsb•6mo ago
You were literally saying "not one" person (period!) wants the ability to control their own device. Clearly such people exist, even if we aren't the majority.

What is wrong about the OPs arguments that suggests a failure of literacy on their part?

If you want a device that is locked down by the manufacturer so it only runs software they approve of, in the name of security, that is a tradeoff you should be allowed to make, and the free market is ready to accomodate your desire. Unfortunately, those of us who want the opposite are not so lucky currently.

Is it really impossible to see for you why some people have a problem with this situation persisting, and with comments like yours further normalizing it?

rcxdude•6mo ago
Hi, also chiming in as someone who also would like to stop cheering when these kinds of vulnerabilities are found, and I'll do it when manufacturers stop treating me, the person buying their products, like the thief in your example.
MattPalmer1086•6mo ago
It's an attack vector that means some of the protection you thought you had if your device is lost or stolen can be bypassed.

You seem to feel there is no benefit to this protection (from non-owners of the device), and instead is protecting the device from the owner. Would you care to expand on that?

ACCount36•6mo ago
DRM keys.

This is exactly the kind of attack that's used to extract DRM keys, which are normally made completely inaccessible to the user by malicious device vendors.