Also having a hard time groking it, but from the README looks like maybe the equivalent to setting up a TOR node to front an ssh daemon and routing a shell through the onion network to get to a host behind a NAT.
I'm thinking the same thing. Is there some kind of circumstance where I'd want to use this instead of SSH? I'm hardly inclined to fix what isn't broken at the best of times, but the p2p element just seems weirdly superfluous.
Accessing a “home computer” behind a NAT you don’t control or has a dynamic IP, eg. computers/devices that only have mobile connection and many (most?) broadband home connections.
I sometimes need to connect to a CI runner to debug some CI build script. I made a (quick hack of a) tool [0] for doing that by creating an Onion service on the runner listening to SSHD, and printing a one-liner I can paste on my dev machine to connect to it via Tor. This sounds like basically the same idea, but using a DHT and hole punching instead of onion routing.
Seems so: I like the idea. Would be, however, to integrate with mosh [1] and feel much better if there was a well audited SSH implementation beneath the hole punching and rendezvous layer.