News for hackers. Stuff that matters.

A comment on Subspace – A simple WireGuard VPN server GUI. Parent comment

Re:Subspace – A simple WireGuard VPN server GUI by OJFord on Wednesday May 20, 2020 @05:52AM (#23245028)
Yes, but just to check / point out that I don't think it's clear in current docs.txt (I know you said they're still WIP) - the 'hoppy server' that I add as a peer would be routed straight through to my own right, as in the public key for 'ca1.hoppy.network' is generated by me?

Or do I have to add a peer that's out of my control, which you use for routing between the two that are under my control?

[ Parent | on HN ]
Re:Subspace – A simple WireGuard VPN server GUI by rubatuga on Wednesday May 20, 2020 @06:05AM (#23245104)
It's the latter, you peer with Hoppy, and then connections to your assigned public IP simply use Hoppy as a "hop" before arriving to you.
[ Parent | on HN ]
Re:Subspace – A simple WireGuard VPN server GUI by OJFord on Wednesday May 20, 2020 @06:08AM (#23245127)
Oh, I'm less keen on that. Doesn't it defeat the point of a secure tunnel if you give away a maintenance shaft in the middle?
[ Parent | on HN ]
Re:Subspace – A simple WireGuard VPN server GUI by BenjiWiebe on Wednesday May 20, 2020 @09:26PM (#23253976)
Correct. But what this does give you is a static publicly routable IPv4 address.
[ Parent | on HN ]