Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Iroh 1.0

iroh.computer

Post reply on HN
Print view View original

171–180 of 488 posts

Re: Iroh 1.0

#171

Post by SillyUsername »

rklaehn wrote: post #16

I am one of the iroh developers. A question that frequently comes up: when will iroh support webrtc, or BLE, or LoRa, or ... Iroh as of now supports only IPv4, IPv6 and relay transports out of the box. There is such a large variety of potentially interesting transports out there that we can't support all of them without turning the codebase into an unmaintainable maze of feature flags. But we have added the ability t…

You may want to consider using a feature flag API if you think it will be unmaintainable.

Strategy patterns and code-centralised feature management ftw :)

Re: Iroh 1.0

#172

Post by porsager »

rklaehn wrote: post #157
porsager wrote: post #149

How is this different from https://holepunch.to/ ?

Holepunch, formerly hypercore, formerly dat, is a great project. Their main language is js, which makes it difficult to embed into anything but js/ts applications. Also, they are very principled when it comes to peer to peer purity, whereas iroh is a bit more pragmatic. We use dedicated relays to faciliate hole punching, whereas holepunch tries to use other peers as a temporary relay for hole punching messages. Anoth…

Thank you so much for the great reply! Answered all my questions - will definitely look closer!

Re: Iroh 1.0

#173

Post by overgard »

This sounds useful, but isn't this the problem that ipv6 is supposed to solve with 128bit addresses? (I'm not really familiar with why IPv6 never really seemed to take off -- does NAT block incoming IPv6 traffic? (I guess that's the other thing -- even though my devices all seem to have IPv6 addresses I can't recall ever using them))

Re: Iroh 1.0

#174

Post by __float »

ben-schaaf wrote: post #136
kkapelon wrote: post #99

Earlier quoted context omitted.

Like https://tailscale.com/docs/features/tsnet ?

From reading that, it lets you establish connections within your tailscale vpn. Iroh let's you establish connections between devices regardless of their network.

I think everyone in this thread agrees on that part already.

The similarities are in an application lib to connect, and that tail net IPs correspond to device keys like in Iroh. The service using the Go library has its own Tailscale identity.

Re: Iroh 1.0

#177

Post by rklaehn »

w10-1 wrote: post #169

I definitely see the value! But I'm not confident I can tell whether there are e.g., security implications, and I couldn't find anything on point in the docs or on github (other than one discussion on authentication that mentions the information disclosed). Would love a whitepaper on that and any other issues adopters should consider.

We should definitely do a better job explaining this.

Regarding security, one thing to be aware of is that iroh connections are just standard QUIC connections secured using standard TLS with the (also standard) raw public keys in TLS extension.

We don't roll our own crypto. What little non-standard crypto we had previously was removed on the path to iroh 1.0.

So iroh connections are just as secure as the QUIC/TLS connections your browser makes to your banking app. Whenever there are some new concerns like for example post quantum security, we can benefit from industry standards.

E.g. we do already support optional post quantum key exchange to secure connections.

https://www.iroh.computer/blog/iroh-post-quantum-handshakes

Re: Iroh 1.0

#178

Post by peddling-brink »

0x59 wrote: post #124

So this could be used as a streamlined way for client devices (mobile phones for example) to phone home to servers (google.com for example) with user data and bypass some local network controls? (DNS block lists, for example) Is there an android SDK available?

I’m thinking similarly. Seems delightful for malware development and exfil. But I haven’t confirmed how the actual connections are made.

Re: Iroh 1.0

#179

Post by teravor »

rklaehn wrote: post #16

I am one of the iroh developers. A question that frequently comes up: when will iroh support webrtc, or BLE, or LoRa, or ... Iroh as of now supports only IPv4, IPv6 and relay transports out of the box. There is such a large variety of potentially interesting transports out there that we can't support all of them without turning the codebase into an unmaintainable maze of feature flags. But we have added the ability t…

    > Tor
https://github.com/n0-computer/iroh-tor-transport

you are using a Tor daemon in it. tor has a rust implementation and when used with rust has stream objects etc.

an example of how it's used can be found in https://gitlab.torproject.org/tpo/core/oniux

Re: Iroh 1.0

#180

Post by Arqu »

pkulak wrote: post #104
handoflixue wrote: post #70

Earlier quoted context omitted.

Excuse my ignorance on the subject, but what does this solve that VPNs didn't already address?

From my VERY brief understanding: this is like if you want the hole-punching of a VPN, but your stuff is public, so not only do you not want all the security of a VPN, but it works against you. But I'm happy to be corrected!

You don't have to have it public. You can have your app gate against any auth method you like to implement on top. And you can have private relays to segregate your traffic and discovery depending on setup.
Post reply on HN