> Dear openvpn-developers,
>
> I'm wondering what is the best way to submit patches to the openvpn
> project. The patch I (er13) added more than a month ago to this
> ticket https://community.openvpn.net/openvpn/ticket/250 has been
> completely ignored. Instead the patch submitted directly to this
Hi,
Gert has already covered the first part of your mail, but I too would like to
thank you for your efforts.
> To the PolarSSL-1.2 support itself: I must confess I didn't test it
> but I believe the new implementation of verify_callback in
> ssl_verify_callback.c is incorrect
> (https://github
Hi,
On Mon, Mar 25, 2013 at 12:35:12AM +0100, Eugene Rudoy wrote:
> Dear openvpn-developers,
>
> I'm wondering what is the best way to submit patches to the openvpn
> project.
Send the patches to the openvpn-devel list, and if you don't hear from us,
keep nagging on the list and in #openvpn-de
Dear openvpn-developers,
I'm wondering what is the best way to submit patches to the openvpn
project. The patch I (er13) added more than a month ago to this ticket
https://community.openvpn.net/openvpn/ticket/250 has been completely
ignored. Instead the patch submitted directly to this list has be
Ack on patches 1-5!
> -Original Message-
> From: steffan.kar...@fox-it.com [mailto:steffan.kar...@fox-it.com]
> Sent: maandag 18 maart 2013 17:37
> To: openvpn-devel@lists.sourceforge.net
> Subject: [Openvpn-devel] PolarSSL 1.2 support, while keeping config
> file com
Hi Everyone,
The attached patches add PolarSSL 1.2 support to OpenVPN 2.3, while maintaining
OpenVPN configuration file compatibility between the OpenSSL and PolarSSL
builds.
Patches 1-3 upgrade the supported PolarSSL versions to 1.2.5 or newer.
Patch 4 adds data channel cipher name compatibil
Hi,
>From PolarSSL 1.1 to 1.2 the cipher names have changed and the API changed a
>bit. This causes the 2.3 release of OpenVPN to be in- compatible with PolarSSL
>1.2.
We've prepared three patches to add support for PolarSSL 1.2 to OpenVPN 2.3.
The first two patches just improve error reportin
