> 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
On 25/03/13 13:31, Arne Schwabe wrote:
> Am 25.03.13 13:20, schrieb David Sommerseth:
>> On 20/03/13 16:49, Siren 1117 wrote:
>>> Hi all,
>>>
>>> I modified the obfuscation patch to work with git-master. And I also put
>>> it on Github: https://github.com/siren1117/openvpn-obfuscation-release .
>>>
Am 25.03.13 13:20, schrieb David Sommerseth:
> On 20/03/13 16:49, Siren 1117 wrote:
>> Hi all,
>>
>> I modified the obfuscation patch to work with git-master. And I also put
>> it on Github: https://github.com/siren1117/openvpn-obfuscation-release .
>>
>> Hope it could help someone.
> Your patch st
On 20/03/13 16:49, Siren 1117 wrote:
> Hi all,
>
> I modified the obfuscation patch to work with git-master. And I also put
> it on Github: https://github.com/siren1117/openvpn-obfuscation-release .
>
> Hope it could help someone.
Your patch still have not changed *anything* commented in this e-
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
