Iroh

Iroh

@iroh.computer

IP addresses break, dial keys instead. I'm iroh.computer from the folks at n0.computer, a modular networking stack in Rust 🦀

1.1K followers8 following155 posts

Iroh reposted

Iroh reposted

Here is an @iroh.computer teaser, showing web browser finding a iroh node (on my machine) replicating two dialog db's that you can connect to via WebRTC transport (without relays)

Iroh reposted

Replying to @rustconf.com

Thank you to our generous Gold sponsor iroh for supporting #rustconf this year! Be sure to connect with their team at #rustconf26 this week. www.iroh.computer

Please be aware that this morning at about 07:10 UTC a malicious version (0.3.10, now removed) of the arrayref crate was published. This crate is a transitive dependency of iroh, via blake3 and might have made it onto your (CI) machine if you happened to cargo update between 07:10 and ~08:10 UTC.

View full thread

Please be careful if any of your CI jobs ran during this period, or if you did a build yourself. Consider the machines and any credentials on it compromised. A simple check is to look for the malicious crates in ~/.cargo/registry/src/, but that is not comprehensive and depends on your setup.

Please be aware that this morning at about 07:10 UTC a malicious version (0.3.10, now removed) of the arrayref crate was published. This crate is a transitive dependency of iroh, via blake3 and might have made it onto your (CI) machine if you happened to cargo update between 07:10 and ~08:10 UTC.

The compromised crate depended on a fake proc-macro1 crate from a typosquatted maintainer. proc-macro1 in turn had a malicious build.rs file which downloaded an unknown payload. That payload remains running afterwards, and connects to 23.254.165.112. More is not yet known about it.

Other popular crates that were compromised at the same time were internment and append-only-vec which also had their dependency changed to the malicious proc-macro1 crate.

Iroh reposted

I’ve been working on an Exaclidraw fork for about a week that syncs your drawings to your Atmosphere account as well as uses Iroh for realtime encrypted end to end collaborative work. I feel like it’s at a stage where I can share it. Meet lexidraw.app!

lexidraw.appLexidraw, an Excalidraw fork where your drawings follow youLexidraw is an Excalidraw fork where your drawings follow you. Share publicly with the Atmosphere or privately with iroh.

At the IETF126 meeting in Vienna this week? Want to chat about iroh? About QUIC? Multipath? Holepunching? Ping us!

Iroh reposted

What a week! 1.0 launch on Monday, 10k stars by Thursday. Thank you so much everyone for all of your support 😊

Let's collect some cool stuff people are building on iroh :) Post your thing and we'll try to repost ✌️ 🧵

View full thread
hazel★@fractal.beauty

congrats on 1.0 @iroh.computer! i use iroh in a desktop+mobile app to get a direct connection between devices by scanning a QR code for fast/cheap/secure file transfer: musicopy.app

Andy Gayton@ndyg.ca

a little util that's become essential in my stack. if you work on remote vms and want to interact with services from your local laptop, pai-sho makes specified ports available on your localhost. ports reconnect when your laptop wakes up. built on @iroh.computer 🙏 github.com/cablehead/pa...

Let's collect some cool stuff people are building on iroh :) Post your thing and we'll try to repost ✌️ 🧵

View full thread

It took us 4 years and 65 releases of iterating on iroh to get to this 1.0. It'll be fun to look back in the coming days & weeks when we'll talk about how iroh evolved to get to this 1.0.

This wouldn't be possible if we hadn't been able to start with Quinn. We never *wanted* to fork Quinn, but here we are. The post also attempts to explain the reasoning!

@pvh.ca speaks truth, but there's one more corner in the design space: you can federate the infrastructure instead of centralizing it. That's the choice we made for iroh relays: you can run your own (it's OSS!), and endpoints connected to your relay can talk to endpoints connected to other relays.

pvh@pvh.ca

All peer-to-peer systems have to compromise one way or another on this: they can decide that direct P2P is essential and simply fail, they can provide centralized fallback alternatives, or they can try to find/convince/incentivize another peer to route traffic on your behalf.

Iroh reposted

Replying to @iroh.computer

The version number doesn't do it justice. This is the foundation for 1.0 and for many exciting features that will happen under the hood during the 1.0 series. It is also a big step for our plan to build iroh on existing IETF RFCs and RFC drafts as much as possible.