Re: [Openvpn-devel] [PATCH (master)] Drop gnu89/c89 support, switch to c99

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 30/08/16 00:20, David Sommerseth wrote: > On 29/08/16 23:32, Steffan Karger wrote: >> HI, > >> On 29 August 2016 at 23:03, David Sommerseth >> wrote: >>> On 29/08/16 22:45, David Sommerseth wrote: On 28/08/16 21:42, Steffan Karger wrote: >>>

Re: [Openvpn-devel] Fixing non-standard PKCS#11 serialization format using a patched pkcs11-helper?

On Mon, 2016-08-29 at 21:55 +0200, David Sommerseth wrote: > There have been some proposals to ditch pkcs11-helper and rather use a > newer and more compliant library instead (p11-kit). I think this > makes more sense, to be honest. There are more issues with > pkcs11-helper which upstream seems

Re: [Openvpn-devel] [PATCH (master)] Drop gnu89/c89 support, switch to c99

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 29/08/16 23:32, Steffan Karger wrote: > HI, > > On 29 August 2016 at 23:03, David Sommerseth > wrote: >> On 29/08/16 22:45, David Sommerseth wrote: >>> On 28/08/16 21:42, Steffan Karger wrote: Previously, we would use the compiler's default

Re: [Openvpn-devel] [PATCH (master)] Drop gnu89/c89 support, switch to c99

HI, On 29 August 2016 at 23:03, David Sommerseth wrote: > On 29/08/16 22:45, David Sommerseth wrote: >> On 28/08/16 21:42, Steffan Karger wrote: >>> Previously, we would use the compiler's default C version, which >>> defaults to gnu89 for GCC < 5, gnu11 for GCC > 5, and c11 for >>> clang, but mi

Re: [Openvpn-devel] [PATCH (master)] Drop gnu89/c89 support, switch to c99

On 29 August 2016 at 21:29, Selva Nair wrote: > > On Sun, Aug 28, 2016 at 3:46 PM, Steffan Karger wrote: >> >> On 28 August 2016 at 21:42, Steffan Karger wrote: >> > Previously, we would use the compiler's default C version, which >> > defaults >> > to gnu89 for GCC < 5, gnu11 for GCC > 5, and c

Re: [Openvpn-devel] [PATCH (master)] Drop gnu89/c89 support, switch to c99

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 29/08/16 22:45, David Sommerseth wrote: > On 28/08/16 21:42, Steffan Karger wrote: >> Previously, we would use the compiler's default C version, which >> defaults to gnu89 for GCC < 5, gnu11 for GCC > 5, and c11 for >> clang, but might even differ

Re: [Openvpn-devel] [PATCH (master)] Drop gnu89/c89 support, switch to c99

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 28/08/16 21:42, Steffan Karger wrote: > Previously, we would use the compiler's default C version, which > defaults to gnu89 for GCC < 5, gnu11 for GCC > 5, and c11 for > clang, but might even differ per distro. > > One of the reasons to accept the

Re: [Openvpn-devel] Fixing non-standard PKCS#11 serialization format using a patched pkcs11-helper?

On 29/08/16 21:55, David Sommerseth wrote: > On 29/08/16 15:02, Samuli Seppänen wrote: >> Hi, >> >> Right now our Windows installers use the official pkcs11-helper >> release from the OpenSC project. Unfortunately this means that >> output of "--show-pkcs11-ids" and input of "--pkcs11-id" are >

Re: [Openvpn-devel] Fixing non-standard PKCS#11 serialization format using a patched pkcs11-helper?

On 29/08/16 15:02, Samuli Seppänen wrote: > Hi, > > Right now our Windows installers use the official pkcs11-helper > release from the OpenSC project. Unfortunately this means that > output of "--show-pkcs11-ids" and input of "--pkcs11-id" are > non-standard, as reported here: > >

Re: [Openvpn-devel] [PATCH (master)] Drop gnu89/c89 support, switch to c99

On Sun, Aug 28, 2016 at 3:46 PM, Steffan Karger wrote: > On 28 August 2016 at 21:42, Steffan Karger wrote: > > Previously, we would use the compiler's default C version, which defaults > > to gnu89 for GCC < 5, gnu11 for GCC > 5, and c11 for clang, but might > even > > differ per distro. > > > >

Re: [Openvpn-devel] Time to change the default cipher?

Hi, On Mon, Aug 29, 2016 at 08:45:52PM +0200, Jan Just Keijser wrote: > uhoh: https://sweet32.info/ > > shall we change the default cipher in the master tree to AES-256 (if not > done so already) ? If a master client talks to a master server, they will negotiate AES-256 automatically, so it's

Re: [Openvpn-devel] [PATCH (master)] Updated build parameters to match openvpn-install-2.3.12-I601

Hi, On Mon, Aug 29, 2016 at 03:30:45PM +0300, Samuli Seppänen wrote: > Arguably we could add openvpnserv2 to 2.3.x, but I would rather focus on > getting 2.4.0 out. This. 2.3 is what it is, and the great stuff happens with 2.4 :-) gert -- USENET is *not* the non-clickable part of WWW!

[Openvpn-devel] Time to change the default cipher?

Hi all, uhoh: https://sweet32.info/ shall we change the default cipher in the master tree to AES-256 (if not done so already) ? share and enjoy, JJK -- ___ Openvpn-devel ma

[Openvpn-devel] Fixing non-standard PKCS#11 serialization format using a patched pkcs11-helper?

Hi, Right now our Windows installers use the official pkcs11-helper release from the OpenSC project. Unfortunately this means that output of "--show-pkcs11-ids" and input of "--pkcs11-id" are non-standard, as reported here: In Fedora this pro

Re: [Openvpn-devel] [PATCH (master)] Updated build parameters to match openvpn-install-2.3.12-I601

Hi, Il 29/08/2016 12:10, Bojan Komazec ha scritto: > Thanks a lot Samuli. > > I cloned "openvpn-build" repo yesterday and created my patch branch off > the last commit on "release/2.3" but after reading your email I checked > it out again and saw that my "release/2.3" was actually 1 commit behind

Re: [Openvpn-devel] [PATCH (master)] Updated build parameters to match openvpn-install-2.3.12-I601

On Mon, Aug 29, 2016 at 10:38 AM, David Sommerseth < open...@sf.lists.topphemmelig.net> wrote: > > On 29/08/16 11:10, Bojan Komazec wrote: > > Thanks a lot Samuli. > > > > I cloned "openvpn-build" repo yesterday and created my patch branch > > off the last commit on "release/2.3" but after reading

Re: [Openvpn-devel] [PATCH (master)] Updated build parameters to match openvpn-install-2.3.12-I601

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 29/08/16 11:10, Bojan Komazec wrote: > Thanks a lot Samuli. > > I cloned "openvpn-build" repo yesterday and created my patch branch > off the last commit on "release/2.3" but after reading your email I > checked it out again and saw that my "releas

Re: [Openvpn-devel] [PATCH (master)] Updated build parameters to match openvpn-install-2.3.12-I601

Thanks a lot Samuli. I cloned "openvpn-build" repo yesterday and created my patch branch off the last commit on "release/2.3" but after reading your email I checked it out again and saw that my "release/2.3" was actually 1 commit behind the origin. I am still trying to understand how this differen

Re: [Openvpn-devel] [PATCH (master)] Updated build parameters to match openvpn-install-2.3.12-I601

Il 29/08/2016 11:05, Bojan Komazec ha scritto: > This is my first attempt to contribute to OpenVpn project. Please let me > know if I am doing it right. Forgot to thank you for your contribution, so here it comes: thank you! :) When you contribute to openvpn-gui, openvpn-build or easy-rsa you can

Re: [Openvpn-devel] [PATCH (master)] Updated build parameters to match openvpn-install-2.3.12-I601

Hi, > OpenVPN/openvpn-build has to be updated so it fetches and builds OpenVpn > v2.3.12. > > From 87a0ca6307ea9c772fc5fa584efc2f2f0f3805a8 Mon Sep 17 00:00:00 2001 > From: Bojan Komazec > > Date: Sun, 28 Aug 2016 20:49:02 +0100 > Subject: [PATCH] Updated build par

Re: [Openvpn-devel] [PATCH (master)] Updated build parameters to match openvpn-install-2.3.12-I601

This is my first attempt to contribute to OpenVpn project. Please let me know if I am doing it right. Thanks, Bojan On Sun, Aug 28, 2016 at 9:18 PM, Bojan Komazec wrote: > OpenVPN/openvpn-build has to be updated so it fetches and builds OpenVpn > v2.3.12. > > From 87a0ca6307ea9c772fc5fa584efc2f