|
|
"Earl A.Killian" <openvpn@xxxxxxxxxxxxxxxxx> said: > The annoyance is that the down script is called with the uid/gid of > --user and --group, unlike the up script, which is called with root > privileges. This means the down script cannot undo the firewall, > routing, and resolv.conf changes that the up script made. I could use > suid to fix this, but it seems that openvpn shouldn't be asymmetric in > this way (there could, for example, be a parent daemon that remains > root that runs the up/down scripts when its unprivileged child tells > it to?). It's been suggested before, and though I agree that --user nobody --down /my-privileged-script is broken, I'm not too excited about the feasible solutions, all of which seem to require forking off new privileged processes, introducing new interprocess communication channels, and protecting those channels from being exploited by lower-privilege processes. James ____________________________________________ Openvpn-users mailing list Openvpn-users@xxxxxxxxxxxxxxxxxxxxx https://lists.sourceforge.net/lists/listinfo/openvpn-users |