Am 29.04.21 um 19:15 schrieb Richard T Bonhomme:
> From: string vest <stringves...@gmail.com>
> 
> Under Windows, programmatically retrieving the parent process ID of
> the openvpn instance which called a script is practically impossible.
> The only sensible way, currently available, is to write a PID file.
> 
> This patch adds a single integer variable, named daemon_pid, to the
> script environment. The value of which is set to the openvpn process
> ID that called the script.
> 
> Providing this variable via the running openvpn process is more secure,
> faster and far less prone to user-error than using a PID file.

Could you explain why you need the process ID of the daemon? I am trying
to figure out why that is needed. I also don't understand the secure in
this context. What are you protecting yourself against? You are not
protecting your script being called from a malicious program as that
could lookup the PID of openvpn and just set the daemon_id variable.

Arne


_______________________________________________
Openvpn-devel mailing list
Openvpn-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/openvpn-devel

Reply via email to