rasengan
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
The great Dr. Orr Dunkelman was admirably vocal in his opposition to the publishing of this draft.
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
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.
I was happy to see the lead of Europe’s PQC team also voted with the cryptographers.
[1] Sadly, I know you are aware.
[1] Not AI codebases (and of course, AI code bases I guess)
A Private (PQ Safe) E-Mail Provider You Can Verify End to End
This is going to be very useful for servers hosted in third party DCs.
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!
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!
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...
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
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!
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.
Latch: Terminal multiplexer, like tmux, with SSH, mosh, and web access built in
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...
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.
Cool project!