Am 07.07.17 um 21:59 schrieb Thomas Veerman via Openvpn-devel:
> When setting the SOCKS proxy through the management interface, the
> socks_proxy_port pointer would be set to a value that's no longer valid
> by the time it's used by do_preresolve_host.
> 
> Signed-off-by: Thomas Veerman <thomas.veer...@wanwire.net>
> ---
>  src/openvpn/init.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/src/openvpn/init.c b/src/openvpn/init.c
> index a54307ad..80a8f5fa 100644
> --- a/src/openvpn/init.c
> +++ b/src/openvpn/init.c
> @@ -150,7 +150,7 @@ management_callback_proxy_cmd(void *arg, const char **p)
>          else if (streq(p[1], "SOCKS"))
>          {
>              ce->socks_proxy_server = string_alloc(p[2], gc);
> -            ce->socks_proxy_port = p[3];
> +            ce->socks_proxy_port = string_alloc(p[3], gc);
>              ret = true;
>          }
>      }
> 


ACK. Probably my fault, when I changed that from int to string.

Arne

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Openvpn-devel mailing list
Openvpn-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/openvpn-devel

Reply via email to