Re: [Openvpn-devel] OpenVPN Versioning

2013-06-12 Thread James Yonan
On 12/06/2013 15:08, Arne Schwabe wrote: Am 12.06.13 21:38, schrieb James Yonan: About finding out which cipher client and server use. I am not really familiar with this code so forgive my stupid question. TLS somehow also does this "select the best cipher to use" dance. Why can't we use the TLS

Re: [Openvpn-devel] OpenVPN Versioning

2013-06-12 Thread Arne Schwabe
Am 12.06.13 21:38, schrieb James Yonan: About finding out which cipher client and server use. I am not really familiar with this code so forgive my stupid question. TLS somehow also does this "select the best cipher to use" dance. Why can't we use the TLS mechanism but have to use our own IV_C

[Openvpn-devel] OpenVPN Versioning

2013-06-12 Thread James Yonan
I'm going to present some ideas and patches to make OpenVPN more solid in the area of versioning. The overall goal is to make OpenVPN more robust with respect to differences between client and server in OpenVPN version, TLS version, protocol capabilities, and config file grammar. Specifically

[Openvpn-devel] [PATCH v2] plugin: Extend the plug-in v3 API to identify the SSL implementation used

2013-06-12 Thread David Sommerseth
From: David Sommerseth OpenVPN would segfault unexpectedly if it would be compiled against PolarSSL and the plug-in would expect OpenSSL, or vice-versa. This segfault would not appear before the plug-in would try to access functions which would be available if the plug-in and OpenVPN uses the sa