search

OrchidTechnologies / orchid

Orchid: VPN, Personal Firewall
https://www.orchid.com/
GNU Affero General Public License v3.0
652 stars 103 forks source link

multihop with quick #65

Closed Xyz00777 closed 3 years ago

Xyz00777 commented 3 years ago

hi everyone, i know there is a form for feature requests but this is so extensive that i think you want to make it explicit again under issues to better track the changes needed and this here as a kind of main issue. the problem i currently see is that when i connect, the node on the other side can see what i want to do through the connection (i know you can't prevent this) and can attribute this activity to my crypto id (as i understand/assume the person should only know the crypto id but in the worst case they can possibly find out the correct ip address). i think it would be a great feature if you could add that you can set if you want to have multihop (similar to tor) so that the exit node doesn't know who i am and the node in the middle (or multiple notes in the middle) forward the data encrypted and also only know the person before and behind but don't know what's in the packet (because it should be encrypted) and also don't know (apart from the previous and next note) where the packet is coming from or going to. Maybe encrypt with multiple keys? i see potential here to correct the security holes the tor network has (even if it's not only vpn) from the beginning so they can't be exploited. of course the prices should then be multiplied by the number of hops. no hops = single 1 hop = double price (one node in between) 2 hops = triple price (two nodes in between) ... and then maybe even adjustable with no matter how many the user wants to have depending on that you should also look at QUIC as a transport layer because this can compensate for the omission of a hop in the multihop or can speed up the connection https://blog.cloudflare.com/the-road-to-quic/ The advantage of this is that the user is even more secure.

Xyz00777 commented 3 years ago

i see a second ago that you provide multihop already, but what is with QUIC for the transport layer?

saurik commented 3 years ago

We already support multi hop (it was a launch feature), and I am likely to support HTTP/3 as an alternative transport when it is ready (though it doesn't really have advantages over WebRTC for anything described in this issue).