To clarify: setting up interfaces/routes as root is no problem, but I don't want any of the protocol/transport/etc. code running as root.
-
-
-
Ok, sure then. It talks out a high port and needs to access a device, so nothing else would require root.
-
Is there a guide anywhere on setting it up this way?
-
not off hand. I did it a long time ago, just need to setup the capabilities right to allow dev access
-
Ideally the invoking process would open /dev/net/tun and pass it in after dropping root.
-
In existing configurations I've seen it wants root to setup if addr/route/etc. after connecting.
-
What I'd really want is to just pick a fake local ip and the networks I want to route, and have the vpn client nat-in-userspace.
-
The threat model is a compromised remote injecting malicious network configuration to client.
End of conversation
New conversation -
-
-
It should split into child that runs as uid openvpn. What's the threat model?
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
So long as it can access /dev/{tun, tap}, yup.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.