News for hackers. Stuff that matters.

rasengan

Re:The $6.3B Binance Hack Was Pulled Off in Just 20 Minutes on Friday October 30, 2026 @11:31AM (#50305346)
Cryptocurrencies give sovereignty over your own money... and all the bells and whistles that come with sovereignty: You're responsible for keeping your own funds, and life, safe.
Re:Making Chicken Transparent Using Dorito Dust on Saturday October 17, 2026 @11:50AM (#50132153)
They used to say Yellow 5 was really bad for males... and it used to specifically say "Yellow 5" in the ingredients. First time I heard it called "Tartrazine!"
Re:Rich Dad Poor Dad author shocks fans with $1.2B debt on Thursday September 03, 2026 @11:21AM (#49551503)
Depends what interest, contingencies and on other information to understand if 1.2B debt is a problem or not. Otherwise, for most UHNW people, debt is just a number on a balance sheet.
I feel really bad for you.

It might actually be wise [1] to create a new, slightly less permissioned license for open source wherein the open is defined as anything that isn’t in a kill or surveillance chain or, more broadly, for military use…

[1] for the community

Re:NSA and IETF, Part 9 on Saturday August 15, 2026 @02:36AM (#49308268)
> Orr Dunkelman

The great Dr. Orr Dunkelman was admirably vocal in his opposition to the publishing of this draft.

Re:NSA and IETF, Part 9 on Saturday August 15, 2026 @02:31AM (#49308238)
RFCs are used by developers as strict guidelines for implementation.

The mere publishing of an RFC has customarily been treated by developers as a stamp of approval from the IETF.

The NSA, contractors and their fans argue that simply adding a "RECOMMENDED=N" in an obscure section of this draft will somehow prevent said implementations in deployments.

However, as an example, Canada's NSA equivalent specifically requested the draft to be published so that they can use it to support their poor choice in deployment of solo ML-KEM nation-wide.

While ML-KEM may be sound, significant bugs in implementations in the wild continue to be published.

To be clear, CRQCs do not exist today.

ECC is battle tested, proven, and is used today.

It makes no sense to delete working cryptography and replace it with potentially buggy, non-battle tested implementations of new cryptography for a threat that does not yet exist today.

Instead, you fight HNDL [1] with hybrid which preserves the safety of today, and hopefully also, tomorrow.

No serious security person should be recommending otherwise which is, perhaps, why some may question the motives of those that are pushing for solo ML-KEM.

[1] Harvest now decrypt later

Re:NSA and IETF, Part 9 on Saturday August 15, 2026 @02:16AM (#49308151)
> A majority (but not a large majority) of cryptography engineers would use hybrids at this point

Actually, based on the WGLC, or the three of them rather, it's pretty clear that Ph.D cryptographers significantly prefer hybrid over pure ML-KEM.

> he'd much rather you believe he's arguing for hybrids against people who are trying to exterminate hybrids.

The brigade by the NSA (6+ votes or more if you include NSA contractors), the AD being former NSA and the moderation of Dr. Bernstein for a footnote seems pretty fair and balanced </sic>.

Meanwhile, the lead of the EU PQC program, professors from several universities, Ph.Ds and, additionally, legendary cryptographers all expressed significant concern and even stronger opposition to the publishing of the draft.

Finally, the chairs refused to share their methodology in determining consensus when asked by several Professors and Ph.Ds.

Re:NSA and IETF: Fairness on Tuesday July 07, 2026 @03:15AM (#48814614)
I certainly find it fascinating that the majority of those in favor come from signal intelligence agencies, while the majority of those against are PhD cryptographers.

I was happy to see the lead of Europe’s PQC team also voted with the cryptographers.

Re:NSA and IETF: Fairness on Tuesday July 07, 2026 @03:10AM (#48814578)
As I thought you were aware [1], RFCs are treated as a green light by industries. In the last call itself, the Canadian Cyber Centre said they would use this RFC in particular to justify recommending solo ML-KEM across their nation, proving this point.

[1] Sadly, I know you are aware.

Re:The US Used to Demand the Best Tech. Now We Ban It on Sunday June 28, 2026 @03:37PM (#48710774)
It’s been like this for a while. Take a technology, call it a weapon and control it. Same playbook.
Re:Previewing GPT‑5.6 Sol: a next-generation model on Friday June 26, 2026 @04:56PM (#48691855)
To be fair, whenever I join a pre-existing code-base [1], it's the same. I have no idea and have to map it out ;)

[1] Not AI codebases (and of course, AI code bases I guess)

The UK can’t block Dissent [1] since it looks like normal HTTPS traffic.

[1] https://godissent.com

Re:Hardware Attestation as Monopoly Enabler on Sunday May 10, 2026 @02:33PM (#48086517)
I agree hw attestation is net negative when forced upon end users. OTOH, when service providers use it, it results in transparency to end users [1] so it's really about how it is used.

[1] https://bmail.ag/verify

Re:Ubuntu 26.04 on Friday April 24, 2026 @01:04AM (#47885763)
> TPM-backed full-disk encryption

This is going to be very useful for servers hosted in third party DCs.

Great question! We rebuild if there's a security update or otherwise every few weeks. We're working on a better method, but right now a few templates can be kept warm so users aren't forced to reboot.

Show HN: Clone, a small Rust VMM, forks VMs in under 20ms via CoW

https://github.com/unixshells/clone

We needed a secure, multi-tenant way to offer shell accounts to users, but most VMMs were using too much memory and containers are unsafe. With clone, VMs are now more memory efficient than containers in most cases.Since many other projects on HN looked like they were doing this too, open sourcing this was the right thing to do.Feel free to use in whole or in part as you see fit!

( Read More... | 3 comments | 3 points | on HN )
Re: on Sunday April 19, 2026 @02:06PM (#47826265)
We needed a secure, multi-tenant way to offer shell accounts to users, but most VMMs were using too much memory and containers are unsafe. With clone, VMs are now more memory efficient than containers in most cases.

Since many other projects on HN looked like they were doing this too, open sourcing this was the right thing to do.

Feel free to use in whole or in part as you see fit!

Re:Do you even need a database? on Wednesday April 15, 2026 @01:18PM (#47782149)
Sounds like a good way to waste the only scarce resource: time.

I built a free SSH relay for homelab machines behind CGNAT

As most of you know, ISPs don't often provide real ingress-routable IP addresses. So I built a free relay system, that works directly with latch [1], a terminal multiplexer with built in SSH/Mosh/etc.It's powered by 9 POPs. latch maintains a QUIC tunnel with your relay, and you connect to whichever is closest to you. Wherever you are in the world, you will be able to connect to a nearby relay...

( Read More... | no comments | on HN )

Show HN: Chrome Developer Tools on Android

Web development on Android has been difficult due to the lack of the full Chrome Dev Tools Suite.We solved this by packaging it with a proxy that bridges them via CDP.It's open source and available on Play!https://unixshells.com/browser.html

( Read More... | no comments | on HN )
Re:Launch HN: Freestyle: Sandboxes for AI Coding Agents on Monday April 06, 2026 @01:56PM (#47664441)
Interesting!

We're working on a similar solution at UnixShells.com [1]. We built a VMM that forks, and boots, in < 20ms and is live, serving customers! We have a lot of great tools available, via MIT, on our github repo [2] as well!

[1] https://unixshells.com

[2] https://github.com/unixshells

Use latch to ssh, mosh or web into your machine. latch multiplexes terminal windows (like screen or tmux).

We built this for use on UnixShells [1].

All remote connections are verified against the authorized_keys and are, of course, end to end encrypted.

This is MIT licensed. There is also a relay that lets you connect to your latch sessions that are behind NAT - this has a small cost to it for infrastructure. However, you can use tailscale/ngrok or your own external IP for free.

https://github.com/unixshells/latch

[1] https://unixshells.com

Show HN: Pure Go mosh client, server, and WASM build for the browser

https://github.com/unixshells/mosh-go

Go implementation of mosh (mobile shell) both client and server and wire-compatible with the core C implementation.The full mosh protocol is implemented including but not limited to AES-128-OCB3, SSP transport with sequencing and retransmission, datagram fragmentation, protobuf state sync, local echo prediction, etc.It compiles to WASM, which is how we run mosh in the browser at UnixShells.com...

( Read More... | 1 comment | on HN )
I don't know if I agree or not with his views, but the fact that he's moving from complaining about something, to doing something about his beliefs, has convinced me to move from a negative to a significantly positive view of him, as a person; to reiterate, regardless of whether I agree with said views.

The will to fight for what one believes in - I think we can all agree that is an admirable human trait that would result, for those who do follow his views, in him being labeled as a hero and defender of people's rights.

Bravo, Garry.

I thought I was reading the Onion. :(
This reminds me of https://wiki.devilfruit.com

Cool project!

Re:Memories of .us on Thursday November 27, 2025 @04:49PM (#46073532)
Some IRC networks still use naming as such like "server.state.country.dal.net."

Older »