matheus23

7 ms·

1.
by matheus23 3mo ago
You need to know the public key you communicate with ahead of connecting to the correct relay. It needs to be shared securely out-of-band, relays don't help with that.
2.
by matheus23 3mo ago
Somewhat easy, unfortunately. If you look at Wireguard traffic, you'll see a <EndpointID>.iroh.invalid SNI in the QUIC Initial packet. Encrypted ClientHello can fix that, but support hasn't shipped into rustls yet. So it&#x2
3.
by matheus23 3mo ago
We keep thinking about ways to combine iroh + zeroMQ! I think these two could compose. (Not familiar with nanomsg myself) About tailscale: It's similar, but iroh is not a VPN, so it doesn't add a TUN interface. Instead, you'd
4.
by matheus23 3mo ago
The secret is that iroh still uses IPs under the hood :) But with QUIC, your connections aren't bound to your four-tuple, your connection can migrate from e.g. WiFi to Cellular with only a small blip/hiccup. And with QUIC multipat
5.
by matheus23 6mo ago
There were experiments :) https://github.com/dignifiedquire/nquinn The cool thing about noq (and Quinn, where we inherited this from), is that you can implement your own "Session" trait. So that can be either
6.
by matheus23 6mo ago
The TLS authentication story is fully configurable. This hasn't changed compared to Quinn. We use noq in iroh, and in iroh we use raw public keys (RFC7250). When you use iroh, you don't need to set up DNS or TLS certificates, you
7.
by matheus23 6mo ago
noq doesn't implement any relaying logic itself. From the perspective of noq, iroh relays are another IP subnet that it's sending packets to and receives packets from, so just another path. > Or is the relayed QUIC wrapped in d
8.
Improving Declarative APIs for Graphics with Types(irreactive.com)
1 points by matheus23 6y ago|0 comments