Am 03.05.21 um 19:22 schrieb tincantech via Openvpn-devel:
> ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
> On Thursday, 29 April 2021 18:15, Richard T Bonhomme <stringves...@gmail.com> 
> wrote:
> 
>> 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.
> 
>> Signed-off-by: Richard T Bonhomme tincant...@protonmail.com
> 
>> src/openvpn/tls_crypt.c | 1 +
>> 1 file changed, 1 insertion(+)
> 
>> diff --git a/src/openvpn/tls_crypt.c b/src/openvpn/tls_crypt.c
>> index 7b5016d3..23d93a6c 100644
>> --- a/src/openvpn/tls_crypt.c
>> +++ b/src/openvpn/tls_crypt.c
>> @@ -537,6 +537,7 @@ tls_crypt_v2_verify_metadata(const struct tls_wrap_ctx 
>> *ctx,
>> setenv_str(es, "script_type", "tls-crypt-v2-verify");
>> setenv_str(es, "metadata_type", metadata_type_str);
>> setenv_str(es, "metadata_file", tmp_file);
> 
>> -   setenv_int(es, "daemon_pid", platform_getpid());
> 
>>     struct argv argv = argv_new();
>>     argv_parse_cmd(&argv, opt->tls_crypt_v2_verify_script);
> 
> 
>> --
>> 2.25.1
> 
> Bump.

Are you trying to annoy the people that review patches? You should be
long enough on the mailing list to understand that reviews in under a
week are not often.

Bumping things with replying "bump" feel like a bad forum etiquette.

Arne


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

Reply via email to