(untitled)

I've built per-PID and per-ip router. It's called obh0d Not A VPN, as VPNs are idiotic pipes This is surgical instrument You pick which PID's and IP's would go through xray + tun2socks tunnel Everything else is going through normal internet All DNS is routed through tunnel by default I wrote this for a client who sells it to russians to bypass restrictions I really want to open-source the project, but I would not do it without his consent He sells it as SaaS for customers All open-source models is like kicking dead whales down the beach delayed source means you get old code source available means u can read it but not use it dual license means free version is like kicking dead whales down the beach no license file would stop some freak from Baranovichi or Xun Pun Pao province to monetize it without consent of the author (me) and my customer if u care about opsec: what would make you trust this enough to pay for it? how can I open-source it without my customer losing money

kek btfo >tun2socks >ip 1 nftables/iptables rule >pid net_cls cgroup + 2 nftables/iptables rules (one to reroute the other to masquerade) >untrusted code double kek, but separate uid + 2 nftables/iptables rules (one to reroute the other to masquerate) and one-two rules to forcibly drop the bad traffic.

>You pick which PID's and IP's would go through xray + tun2socks tunnel Shit. Not per-IP: a lot of sites behind the same anti-ddos/CDN have the same IP. A browser addon that possesses the knowledge inside of TLS is better - and there are plenty addons like that.

>>89134 >there are plenty addons like that. Which ones?

>>89130 I like the idea of fine-grained control over tunneling. I'm currently using netns/iptables and firefox containers for this, but tools for normal people are definitely lacking in this area, so you might become a pioneer if you make this user-friendly.