frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Keys Not Included: recovering the signing keys for US driver's license barcodes

https://ryan.science/blog/keys-not-included
62•Ryan5453•1h ago•16 comments

Nvidia announces native GPU programming in Rust

https://developer.nvidia.com/blog/introducing-cuda-rust-two-tracks-for-writing-gpu-kernels/
449•nonmaskable•17h ago•158 comments

The Painful Truth: The RAM Crisis Is Only Just the Beginning

https://www.madshrimps.be/news/the-painful-truth-the-ram-crisis-is-only-just-the-beginning/
20•perelin•43m ago•16 comments

Training a 4B model to produce 81% faster query plans than Postgres

https://rohanbansal.com/qorl
453•polyphilz•9h ago•94 comments

DeepSeek-v4.1 Flash: Pushing the Limits of KV Cache Compression

https://zartbot.github.io/blog/model_arch/dsv41flash_arch/en.html
70•mfiguiere•3h ago•6 comments

Xiaomi Mimo 2.6 live post-training dashboard

https://mimo.xiaomi.com/rl/
322•krackers•8h ago•86 comments

Backups Aren't Simple

https://filipovski.net/2026/09/16/backups-arent-simple.html
137•afilipovski•8h ago•73 comments

Breaking the 1.58-bit Barrier for Ternary LLMs

https://arxiv.org/abs/2609.16338
163•matt_d•7h ago•22 comments

Small programming tricks

https://will-keleher.com/posts/small-programming-tricks-matter/
442•signa11•12h ago•199 comments

Developing provably correct Rust code with Verus

https://www.amazon.science/blog/developing-provably-correct-rust-code-with-verus
57•Betelbuddy•2d ago•9 comments

The engineering behind the US Strategic Petroleum Reserve

https://johnjwang.com/post/2026/09/15/engineering-behind-us-strategic-petroleum-reserve
152•johnjwang•1d ago•57 comments

OpenSpec – A lightweight and configurable AI spec framework

https://openspec.dev/
100•etoxin•5h ago•38 comments

A 32-Year-Old Bug Walks into a Telnet Server

https://labs.watchtowr.com/a-32-year-old-bug-walks-into-a-telnet-server-gnu-inetutils-telnetd-cve...
13•paimapi•1d ago•1 comments

The Return of Sail Power: Cargo Ships Are Turning Back to the Wind

https://gcaptain.com/the-return-of-sail-power-cargo-ships-are-turning-back-to-the-wind/
41•gumby•4h ago•18 comments

Performance Improvements in .NET 11

https://devblogs.microsoft.com/dotnet/performance-improvements-in-net-11/
222•soheilpro•1d ago•40 comments

AWS says it can't restore some data from mideast facilities struck by Iran

https://www.wsj.com/world/middle-east/aws-says-it-cant-restore-some-data-from-mideast-facilities-...
290•berkeleyjunk•1d ago•237 comments

PCB is brought to you by Fable 5

https://a6mzero.com/posts/this-pcb-is-brought-to-you-by-fable-5/
45•jasonpeacock•2d ago•14 comments

Reversing Factorio's RNG

https://gegell.github.io/posts/factorio-rng/
167•jheitmann•4d ago•21 comments

Part-human part-mouse brain developed in science breakthrough

https://www.bbc.com/news/articles/c60m3k28j81mo
13•marc__1•3h ago•10 comments

HarnessTax: How Much Does the Harness Matter for Coding Agents?

https://harnesstax.github.io/
73•matt_d•6h ago•21 comments

Show HN: An e-ink frame that hears birds and draws them as 1800s illustrations

https://github.com/arnegiacomo/fugleramme
2117•arnemunthekaas•1d ago•240 comments

Japan's book scene is moving from bookstores to libraries

https://untranslatedjp.substack.com/p/japans-book-scene-is-quietly-moving
140•herbertl•4d ago•55 comments

Anecdotally, programmers dislike "reduce"

https://evanhahn.com/posts/2026-09-13-programmers-dislike-reduce/
118•vinhnx•2d ago•186 comments

Mapsnap: Automated Georeferencing for Historic Sanborn Insurance Maps

https://www.danvk.org/2026/09/10/mapsnap.html
12•evakhoury•1d ago•2 comments

Reverse-engineered Jev-like model

https://github.com/vinnylarouge/jevlike
96•rochansinha•9h ago•15 comments

Dream-RSI: Recursive Self-Improvement through Evolving Worlds

https://arxiv.org/abs/2609.14858
187•bananaflag•14h ago•49 comments

Anatomy of a Texture

https://agentlien.github.io/texture/
83•Agentlien•14h ago•14 comments

Monsanto's Cruel, and Dangerous, Monopolization on American Farming (2008)

https://www.vanityfair.com/news/2008/05/monsanto200805
26•kamaraju•2h ago•9 comments

Hackers Got Inside a Flock Camera

https://www.wired.com/story/hackers-flock-camera-data-shows-how-system-works/
496•driverdan•15h ago•231 comments

Accurate Models of AMD Matrix Cores

https://arxiv.org/abs/2609.14845
69•matt_d•9h ago•9 comments
Open in hackernews

Keys Not Included: recovering the signing keys for US driver's license barcodes

https://ryan.science/blog/keys-not-included
60•Ryan5453•1h ago

Comments

jmathai•51m ago
I come to HN to learn things I never realized I wanted to know.
simoncion•51m ago
At the time of this writing, the subtitle of the submission here on HN is

  recovering the signing keys for US driver's license barcodes
Notably, this subtitle doesn't appear on the blog post.

Anyway. I only see claims that the public key can be determined from license barcodes, not that a signing key can be determined. What am I missing or misunderstanding?

To head off one potential retort: While it's true that one can use a public key to encrypt data for the recipient that has the private half of that key or verify that data has been signed by the possessor of the private half of that key, I'm almost 100% certain that it's not possible to use that public key to sign data would validate to other folks as being signed by the private half of that key. It has been more than a decade since I've thought about any of this, but isn't the entire point of public-key cryptography that the public part can be distributed to your worst enemy without causing you any trouble at all?

trollbridge•48m ago
Yes. The subtitle is wrong. He recovers the public key, due to the way EDCSA signing works.
kccqzy•34m ago
Yup. The person who submitted this to HN is probably way less knowledgeable on this topic than the writer of the article. The article clearly labels the recovered keys as “recovered public keys” at the top.
otterley•26m ago
Given the poster's nickname, the person who posted it and the author may be one and the same.
kccqzy•23m ago
I think the author is Claude.
piratejon•44m ago
That's really neat! Seems potentially adaptable to paper currency--a verifiable QR code digital signature of the bill's serial number creates a cryptographically hard obstacle to counterfeiting!
kqp•29m ago
Copy known good serial number + signature.
KingMachiavelli•41m ago
All of this is nearly pointless unless the photo itself is in the barcode and also signed. You only need a leak of a few hundred real IDs to cover all of the identifiable characteristics (hair, eye, skin color, approx height and weight). Leak a few hundred thousand a year and now you can’t even flag leaked IDs without some false positives.

A fake photo plus a valid barcode will pass any current check right? Unless you still do a secondary proprietary photo lookup that I don’t think exists.

kccqzy•20m ago
I wonder if we might have the equivalent of Certificate Revocation List for IDs leaked this way.
RockRobotRock•37m ago
I had a fake ID, and it being scannable was a huge selling point. Convenience stores all scan, and don't seem to care if you look underage. I was only turned down two or three times, usually at bars and restaurants.
NDlurker•27m ago
The other thing I remember was California fakes folding in half and not breaking
bzmrgonz•32m ago
It baffles that people think it's a bad thing to disclose a public key. That's their purpose actually. Sure we now have the post quantum computer threat, and some state actors are harvesting keys, but quantum computer is going to disrupt so much, that Id verification won't even matter really.
EPWN3D•22m ago
> Before signing, the encoder fills the field with a placeholder (0), repeated for the field's exact length - signs the entire payload including that placeholder, and then writes the real signature over the top of it. To verify, you put the placeholder back.

I hate shit like this. Do not let your crypto layer know about the structure of what it's signing. Keep security stupid.

lazide•18m ago
Counterpoint - every real world crypto algo needs to do somewhat content aware padding or the crypto is much easier to break. Either that, or go so overboard on randomness that it adds a lot of overhead.

When you look at the details underneath more crypto, there is a lot of ah hah - and ‘doh’ - moments due to implementation realities.

foresto•14m ago
https://web.archive.org/web/20260917035309/https://ryan.scie...