[Openvpn-devel] [PATCH] Backported pkcs11-related parts of 7a8d707237bb18 to 2.2 branch

From: Samuli Seppänen Fixes https://community.openvpn.net/openvpn/ticket/145 --- win/config.h.in |4 +++- win/msvc.mak.in | 11 --- win/settings.in |4 3 files changed, 15 insertions(+), 4 deletions(-) diff --git a/win/config.h.in b/win/config.h.in index 82344a0..09263d3

Re: [Openvpn-devel] [PATCH] Backported pkcs11-related parts of 7a8d707237bb18 to 2.2 branch

Just for clarification... this patch adds pkcs11 build option support to Python/Visual Studio build system and thus allows fixing this bug: > From: Samuli Seppänen > > Fixes https://community.openvpn.net/openvpn/ticket/145 > --- > win/config.h.i

Re: [Openvpn-devel] Problem with alloc_buf_gc function

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 13/12/11 21:22, Tiran Kaskas wrote: > The problem is that the nl package was built with 2.1 version, and I > have used this. > > On a different topic: I found an issue, you probably want to fix > that: In reliable_pid_in_range1() function, the thir

Re: [Openvpn-devel] Problem with alloc_buf_gc function

Thanks. Already done the ssl part, only polarssl. It is working perfect and does support 16bit with no change. -Original Message- From: David Sommerseth [mailto:openvpn.l...@topphemmelig.net] Sent: Wednesday, December 14, 2011 10:52 AM To: Tiran Kaskas Cc: Adriaan de Jong; Gert Doering;

Re: [Openvpn-devel] Problem with alloc_buf_gc function

I think Polar even supports 8-bit architectures, but don't quote me on that :). Adriaan > -Original Message- > From: Tiran Kaskas [mailto:tiran.kas...@telit.com] > Sent: woensdag 14 december 2011 9:54 > To: David Sommerseth > Cc: Adriaan de Jong; Gert Doering; openvpn-devel@lists.sourcefo

Re: [Openvpn-devel] Problem with alloc_buf_gc function

"Tiran Kaskas" wrote: Already done the ssl part, only polarssl. It is working perfect and does support 16bit with no change. You got all the data in PolarSSL, LZO and OpenVPN to fit in a 16-bit data-segment of 64 kByte? I'll be amazed. What memory model would be needed to link in all the cod

Re: [Openvpn-devel] Problem with alloc_buf_gc function

Indeed, a large model is used -Original Message- From: Gisle Vanem [mailto:gva...@broadpark.no] Sent: Wednesday, December 14, 2011 11:45 AM To: openvpn-devel@lists.sourceforge.net Subject: Re: [Openvpn-devel] Problem with alloc_buf_gc function "Tiran Kaskas" wrote: > Already done the s

Re: [Openvpn-devel] [PATCH] Backported pkcs11-related parts of 7a8d707237bb18 to 2.2 branch

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 14/12/11 09:36, sam...@openvpn.net wrote: > From: Samuli Seppänen > > Fixes https://community.openvpn.net/openvpn/ticket/145 --- > win/config.h.in |4 +++- win/msvc.mak.in | 11 --- > win/settings.in |4 3 files changed, 15 i

[Openvpn-devel] [PATCH] Fix compiling with --disable-crypto and/or --disable-ssl

The checks introduced in commit 0f2bc0dd92f43c91e33bba8a66b06b98f281efc1 didn't properly remove checks if crypto or SSL was disabled at compile time. Signed-off-by: David Sommerseth --- options.c | 10 +- 1 files changed, 5 insertions(+), 5 deletions(-) diff --git a/options.c b/option

[Openvpn-devel] (no subject)

Re: [Openvpn-devel] [PATCH] Fix compiling with --disable-crypto and/or --disable-ssl

Hi, On Wed, Dec 14, 2011 at 06:15:19PM +0100, David Sommerseth wrote: > The checks introduced in commit 0f2bc0dd92f43c91e33bba8a66b06b98f281efc1 > didn't properly remove checks if crypto or SSL was disabled at compile time. ACK. Nasty #idef's, good that we have Buildbot to tell us :-) gert --