Your patch has been applied to the master and release/2.3 branch.
commit abe18c69a61b42e5ac68b77f66198fc15be99e31 (master)
commit d40de75fea9c9fa17b68e13be67731b6ccec9fb5 (release/2.3)
Author: Gert Doering
List-Post: openvpn-devel@lists.sourceforge.net
Date: Fri Apr 25 21:19:15 2014 +0200
On 25.04.2014 21:19, Gert Doering wrote:
Part of the information was confusing, part was outdated, and part was
just not making sense. Pointed out in trac#348.
Also add note about Linux IPv4-mapped issues as per trac#306.
ACK as per discussion on #openvpn-devel.
Arne
Part of the information was confusing, part was outdated, and part was
just not making sense. Pointed out in trac#348.
Also add note about Linux IPv4-mapped issues as per trac#306.
Signed-off-by: Gert Doering
---
doc/openvpn.8 | 28
1 file changed, 16 insertions(+)
Part of the information was confusing, part was outdated, and part was
just not making sense.
Pointed out in trac#348.
Also add note about Linux IPv4-mapped issues as per trac#306.
Signed-off-by: Gert Doering
---
doc/openvpn.8 | 29 +
1 file changed, 17 insertions(+
Hi,
On Fri, Apr 25, 2014 at 08:37:37PM +0200, Gert Doering wrote:
> Patch has been applied to the master and release/2.3 branches.
>
> commit 661d914c8732a208580b1eab167255c85da162c9 (master)
> commit fc759c2eb4fbf0792d0052966fcf36efebc5bf5d (master)
The second line is release/2.3, obviously. S
As announced at the IRC meeting yesterday, I decided to apply lazy ACK
rules here. The code is tested, fixes an actual bug, and nobody NAKed
it for 4 months...
Patch has been applied to the master and release/2.3 branches.
commit 661d914c8732a208580b1eab167255c85da162c9 (master)
commit fc759c2e
Your patch has been applied to the master and release/2.3 branches.
I've counted the result from yesterday's IRC discussion plus the mail
thread as "ACK from James and me", and Steffan agreed as well (canceling
his initial NAK).
commit 959d60789b6f0bd74296600f58f626cfa9738f78 (master)
commit d160
Hi,
On Thu, Apr 17, 2014 at 01:58:02AM -0600, James Yonan wrote:
> If we keep the current behavior (PolarSSL serial numbers are hex while
> OpenSSL are decimal) then we should at least mark the serial number when
> it's hex, so client software can distinguish it.
>
> This very simple patch does
Your patch has been applied to the master branch.
commit cdbd56ceeae4ef6352e19814447d402d0b5468c0
Author: Steffan Karger
List-Post: openvpn-devel@lists.sourceforge.net
Date: Thu Apr 24 00:43:38 2014 +0200
Add an elliptic curve testing cert chain to the sample keys
Signed-off-by: Stef
Your patch has been applied to the master branch.
commit 609e8131427686adca9b4ed2db44db4aaa920a01
Author: Steffan Karger
List-Post: openvpn-devel@lists.sourceforge.net
Date: Thu Apr 24 00:31:08 2014 +0200
Add support for elliptic curve diffie-hellmann key exchange (ECDH)
Signed-off-b
The return value of x509_get_numeric_string() was interpreted incorrectly
by ssl_verify_polarssl.c's x509_verify_cert_eku(). This patch enables the
usage of oid represenation in --remote-cert-eku options.
Signed-off-by: Steffan Karger
---
src/openvpn/ssl_verify_polarssl.c | 2 +-
1 file changed,
Am 24.04.14 23:02, schrieb Steffan Karger:
> On 24-04-14 00:43, Steffan Karger wrote:
>> [ ECDH patch ]
> ... and attached a v3 of this patch with better debug / warning messages
> when using an OpenSSL build without EC-crypto.
ACK to this version
12 matches
Mail list logo
