Re: [Openvpn-devel] Topics for today's meeting

2011-11-24 Thread Alon Bar-Lev 
My build script is working as-is with cygwin, compiling native win32 binaries!

2011/11/24 Alon Bar-Lev :
> I am *VERY* impressed from cygwin jump, I must admit I have not kept
> track on this project for a long time!
> But now it is up to date with fully operational native windows tools.
> I've done some testing, and it looks like ./configure
> --host=x86_64-w64-mingw32 or i686-w64-mingw will actually work!
> I will build with dependencies now, it will take some time.
>
> 2011/11/24 Alon Bar-Lev :
>> Correction!
>> cygwin provides mingw-w64 now!!!
>> Also recent autoconf/automake/libtool.
>> So we can also cross compile using mingw.
>>
>> 2011/11/24 Alon Bar-Lev :
>>> Hello,
>>>
>>> I won't participate in sync meeting don't have the time.
>>> Anyway, for windows build.
>>> I already provide binaries for OpenVPN using mingw-w64 project, and it
>>> works fine!
>>> I use mingw-w64 for both win32 and win64 binaries, much better than
>>> old mingw project, as mingw-w64 is maintained!
>>> You can see my build system at [1][2].
>>> So mingw cross compile is supported. I would have re-written the
>>> openvpn autoconf script to clean it up and make it more standard, but
>>> current is enough to be usable.
>>>
>>> msys can be used on Windows to build not sure it worth the effort...
>>> mingw can be used with -mno-cygwin parameter, but from my experience
>>> the toolchain in cygwin are way too old to be usable.
>>>
>>> For the tap driver, I always note this... IT SHOULD BE SEPARATE MSI
>>> and SEPARATE PROJECT.
>>> There should be absolutely no dependency between openvpn release cycle
>>> and tap release cycle.
>>> It is just like wireshark and libpcap projects.
>>> OpenVPN installer can embed the tap msi and run it during installation.
>>> When tap installed, it should register its version in registry key, so
>>> openvpn may read it in order to connect (currently it is done
>>> hardcoded within openvpn).
>>>
>>> The TAP driver should be built and signed using Microsoft toolchain,
>>> there is no problem in that. There is almost a single developer for
>>> the tap driver..
>>> The usermode components may be signed on Linux using the
>>> osslsigncode[3], so actual signing is not an issue, if this is desired
>>> I can submit a patch for "make install" to sign, as I do in other
>>> projects.
>>>
>>> Most (99%) users are interested in building custom user mode component
>>> only, so there is no sense in keeping the tap driver as dependency
>>> (build and sign).
>>>
>>> Regards,
>>> Alon.
>>>
>>> [1] https://www.opensc-project.org/build/
>>> [2] https://www.opensc-project.org/build/browser
>>> [3] http://sourceforge.net/projects/osslsigncode/
>>>
>>> 2011/11/24 Samuli Seppänen 

 Hi,

 We're having an IRC meeting today, starting at 18:00 UTC on
 #openvpn-de...@irc.freenode.net. Current topic list is here:

 

 If you have any other things you'd like to bring up, respond to this
 mail, send me mail privately or add them to the list yourself.

 In case you can't attend the meeting, please feel free to make comments
 on the topics by responding to this email or to the summary email sent
 after the meeting.

 NOTE: It's required to use a registered Freenode IRC nickname to join
 #openvpn-devel - look here for details:

 

 --
 Samuli Seppänen
 Community Manager
 OpenVPN Technologies, Inc

 irc freenode net: mattock

 --
 All the data continuously generated in your IT infrastructure
 contains a definitive record of customers, application performance,
 security threats, fraudulent activity, and more. Splunk takes this
 data and makes sense of it. IT sense. And common sense.
 http://p.sf.net/sfu/splunk-novd2d
 ___
 Openvpn-devel mailing list
 Openvpn-devel@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/openvpn-devel
>>>
>>
>

Re: [Openvpn-devel] Topics for today's meeting

2011-11-24 Thread Gert Doering 
Hi,

On Thu, Nov 24, 2011 at 10:58:50AM +0100, Jan Just Keijser wrote:
> +1 autoconf
> -9 CMake

+1 autoconf
-450 anything that requires installation of additional tools on unix systems

(I wouldn't mind if anyone were to create a cmake build environment for
windows, documents that, and commits to maintaining it for a while - but 
please do not convolute the working unix build environment we have right 
now)

gert
-- 
USENET is *not* the non-clickable part of WWW!
   //www.muc.de/~gert/
Gert Doering - Munich, Germany g...@greenie.muc.de
fax: +49-89-35655025g...@net.informatik.tu-muenchen.de


pgp_7QPXycTZw.pgp
Description: PGP signature

Re: [Openvpn-devel] Topics for today's meeting

2011-11-24 Thread Alon Bar-Lev 
I am *VERY* impressed from cygwin jump, I must admit I have not kept
track on this project for a long time!
But now it is up to date with fully operational native windows tools.
I've done some testing, and it looks like ./configure
--host=x86_64-w64-mingw32 or i686-w64-mingw will actually work!
I will build with dependencies now, it will take some time.

2011/11/24 Alon Bar-Lev :
> Correction!
> cygwin provides mingw-w64 now!!!
> Also recent autoconf/automake/libtool.
> So we can also cross compile using mingw.
>
> 2011/11/24 Alon Bar-Lev :
>> Hello,
>>
>> I won't participate in sync meeting don't have the time.
>> Anyway, for windows build.
>> I already provide binaries for OpenVPN using mingw-w64 project, and it
>> works fine!
>> I use mingw-w64 for both win32 and win64 binaries, much better than
>> old mingw project, as mingw-w64 is maintained!
>> You can see my build system at [1][2].
>> So mingw cross compile is supported. I would have re-written the
>> openvpn autoconf script to clean it up and make it more standard, but
>> current is enough to be usable.
>>
>> msys can be used on Windows to build not sure it worth the effort...
>> mingw can be used with -mno-cygwin parameter, but from my experience
>> the toolchain in cygwin are way too old to be usable.
>>
>> For the tap driver, I always note this... IT SHOULD BE SEPARATE MSI
>> and SEPARATE PROJECT.
>> There should be absolutely no dependency between openvpn release cycle
>> and tap release cycle.
>> It is just like wireshark and libpcap projects.
>> OpenVPN installer can embed the tap msi and run it during installation.
>> When tap installed, it should register its version in registry key, so
>> openvpn may read it in order to connect (currently it is done
>> hardcoded within openvpn).
>>
>> The TAP driver should be built and signed using Microsoft toolchain,
>> there is no problem in that. There is almost a single developer for
>> the tap driver..
>> The usermode components may be signed on Linux using the
>> osslsigncode[3], so actual signing is not an issue, if this is desired
>> I can submit a patch for "make install" to sign, as I do in other
>> projects.
>>
>> Most (99%) users are interested in building custom user mode component
>> only, so there is no sense in keeping the tap driver as dependency
>> (build and sign).
>>
>> Regards,
>> Alon.
>>
>> [1] https://www.opensc-project.org/build/
>> [2] https://www.opensc-project.org/build/browser
>> [3] http://sourceforge.net/projects/osslsigncode/
>>
>> 2011/11/24 Samuli Seppänen 
>>>
>>> Hi,
>>>
>>> We're having an IRC meeting today, starting at 18:00 UTC on
>>> #openvpn-de...@irc.freenode.net. Current topic list is here:
>>>
>>> 
>>>
>>> If you have any other things you'd like to bring up, respond to this
>>> mail, send me mail privately or add them to the list yourself.
>>>
>>> In case you can't attend the meeting, please feel free to make comments
>>> on the topics by responding to this email or to the summary email sent
>>> after the meeting.
>>>
>>> NOTE: It's required to use a registered Freenode IRC nickname to join
>>> #openvpn-devel - look here for details:
>>>
>>> 
>>>
>>> --
>>> Samuli Seppänen
>>> Community Manager
>>> OpenVPN Technologies, Inc
>>>
>>> irc freenode net: mattock
>>>
>>> --
>>> All the data continuously generated in your IT infrastructure
>>> contains a definitive record of customers, application performance,
>>> security threats, fraudulent activity, and more. Splunk takes this
>>> data and makes sense of it. IT sense. And common sense.
>>> http://p.sf.net/sfu/splunk-novd2d
>>> ___
>>> Openvpn-devel mailing list
>>> Openvpn-devel@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/openvpn-devel
>>
>

Re: [Openvpn-devel] Topics for today's meeting

2011-11-24 Thread Jan Just Keijser 
Alon Bar-Lev wrote:
> I hate CMake, it is way too complex, these guys re-invented the wheel
> with no decent reuse of any methodology / language that existed
> before.
>   
I agree with Alon here :

+1 autoconf
-9 CMake

esp troubleshooting a non-working CMake setup is a nightmare.

JJK
> If we take SCons as another example, it took python and used it to do
> build... So if you are python developer most probably you know how to
> SCons.
> Also, look the huge backlog of bugs of CMake, it is amazing!
>
> Common to both CMake and SCons is the ability to work with Microsoft
> toolchain to produce binaries. This is a great advantage over the
> autotools. However, these tools are inferior when it comes to
> autotools (provided you know what you are doing) in *NIX, embedded and
> cross compile.
>
> To build using CMake or SCCons you need these tools on *TARGET*
> machine, these tools has LONG LIST of dependencies. To build using
> autotools you need POSIX utils (sh, sed, ls, rm, ...) and POSIX make
> and that's it!
>
> I don't mind if for Windows CMake/SCons will be maintain in addition,
> keep autotools usage for windows cross compile and *NIX build using
> autotools.
>
> Alon.
>
> On Thu, Nov 24, 2011 at 11:25 AM, Adriaan de Jong  wrote:
>   
>> Just to put in my 2cents on the build options: there is a tool that supports 
>> all of those environments (gmake, cygwin, mingw, nmake, visual studio, 
>> eclipse, ), and that's CMake. It's widely used, and has a pretty good 
>> track record. It can also support automated test environments and packaging.
>>
>> It has one major disadvantage: the current build system would need to be 
>> converted from an autoconf-based to a new CMake-based system, together with 
>> all of the knowledge contained within it. Further, there is less knowledge 
>> of CMake than autoconf within the OpenVPN community.
>>
>> Disclaimer: I'm not trying to start a holy war here, I know every system has 
>> its own advantages and drawbacks. I just want to get the option on the table 
>> :). I've had some positive experience with CMake, through PolarSSL and some 
>> projects at work. I'll try to make it to the meeting this evening for the 
>> discussion.
>>
>> Kind Regards,
>>
>> Adriaan
>>
>> 
>>> -Original Message-
>>> From: Samuli Seppänen [mailto:sam...@openvpn.net]
>>> Sent: donderdag 24 november 2011 9:48
>>> To: openvpn-devel@lists.sourceforge.net
>>> Subject: [Openvpn-devel] Topics for today's meeting
>>>
>>> Hi,
>>>
>>> We're having an IRC meeting today, starting at 18:00 UTC on #openvpn-
>>> de...@irc.freenode.net. Current topic list is here:
>>>
>>> 
>>>
>>> If you have any other things you'd like to bring up, respond to this
>>> mail, send me mail privately or add them to the list yourself.
>>>
>>> In case you can't attend the meeting, please feel free to make comments
>>> on the topics by responding to this email or to the summary email sent
>>> after the meeting.
>>>
>>> NOTE: It's required to use a registered Freenode IRC nickname to join
>>> #openvpn-devel - look here for details:
>>>
>>>

Re: [Openvpn-devel] Topics for today's meeting

2011-11-24 Thread Alon Bar-Lev 
I hate CMake, it is way too complex, these guys re-invented the wheel
with no decent reuse of any methodology / language that existed
before.
If we take SCons as another example, it took python and used it to do
build... So if you are python developer most probably you know how to
SCons.
Also, look the huge backlog of bugs of CMake, it is amazing!

Common to both CMake and SCons is the ability to work with Microsoft
toolchain to produce binaries. This is a great advantage over the
autotools. However, these tools are inferior when it comes to
autotools (provided you know what you are doing) in *NIX, embedded and
cross compile.

To build using CMake or SCCons you need these tools on *TARGET*
machine, these tools has LONG LIST of dependencies. To build using
autotools you need POSIX utils (sh, sed, ls, rm, ...) and POSIX make
and that's it!

I don't mind if for Windows CMake/SCons will be maintain in addition,
keep autotools usage for windows cross compile and *NIX build using
autotools.

Alon.

On Thu, Nov 24, 2011 at 11:25 AM, Adriaan de Jong  wrote:
> Just to put in my 2cents on the build options: there is a tool that supports 
> all of those environments (gmake, cygwin, mingw, nmake, visual studio, 
> eclipse, ), and that's CMake. It's widely used, and has a pretty good 
> track record. It can also support automated test environments and packaging.
>
> It has one major disadvantage: the current build system would need to be 
> converted from an autoconf-based to a new CMake-based system, together with 
> all of the knowledge contained within it. Further, there is less knowledge of 
> CMake than autoconf within the OpenVPN community.
>
> Disclaimer: I'm not trying to start a holy war here, I know every system has 
> its own advantages and drawbacks. I just want to get the option on the table 
> :). I've had some positive experience with CMake, through PolarSSL and some 
> projects at work. I'll try to make it to the meeting this evening for the 
> discussion.
>
> Kind Regards,
>
> Adriaan
>
>> -Original Message-
>> From: Samuli Seppänen [mailto:sam...@openvpn.net]
>> Sent: donderdag 24 november 2011 9:48
>> To: openvpn-devel@lists.sourceforge.net
>> Subject: [Openvpn-devel] Topics for today's meeting
>>
>> Hi,
>>
>> We're having an IRC meeting today, starting at 18:00 UTC on #openvpn-
>> de...@irc.freenode.net. Current topic list is here:
>>
>> 
>>
>> If you have any other things you'd like to bring up, respond to this
>> mail, send me mail privately or add them to the list yourself.
>>
>> In case you can't attend the meeting, please feel free to make comments
>> on the topics by responding to this email or to the summary email sent
>> after the meeting.
>>
>> NOTE: It's required to use a registered Freenode IRC nickname to join
>> #openvpn-devel - look here for details:
>>
>> > nnel>
>>
>> --
>> Samuli Seppänen
>> Community Manager
>> OpenVPN Technologies, Inc
>>
>> irc freenode net: mattock
>>
>> ---
>> ---
>> All the data continuously generated in your IT infrastructure contains
>> a definitive record of customers, application performance, security
>> threats, fraudulent activity, and more. Splunk takes this data and
>> makes sense of it. IT sense. And common sense.
>> http://p.sf.net/sfu/splunk-novd2d
>> ___
>> Openvpn-devel mailing list
>> Openvpn-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/openvpn-devel
>
> --
> All the data continuously generated in your IT infrastructure
> contains a definitive record of customers, application performance,
> security threats, fraudulent activity, and more. Splunk takes this
> data and makes sense of it. IT sense. And common sense.
> http://p.sf.net/sfu/splunk-novd2d
> ___
> Openvpn-devel mailing list
> Openvpn-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/openvpn-devel
>

Re: [Openvpn-devel] Topics for today's meeting

2011-11-24 Thread Alon Bar-Lev 
Correction!
cygwin provides mingw-w64 now!!!
Also recent autoconf/automake/libtool.
So we can also cross compile using mingw.

2011/11/24 Alon Bar-Lev :
> Hello,
>
> I won't participate in sync meeting don't have the time.
> Anyway, for windows build.
> I already provide binaries for OpenVPN using mingw-w64 project, and it
> works fine!
> I use mingw-w64 for both win32 and win64 binaries, much better than
> old mingw project, as mingw-w64 is maintained!
> You can see my build system at [1][2].
> So mingw cross compile is supported. I would have re-written the
> openvpn autoconf script to clean it up and make it more standard, but
> current is enough to be usable.
>
> msys can be used on Windows to build not sure it worth the effort...
> mingw can be used with -mno-cygwin parameter, but from my experience
> the toolchain in cygwin are way too old to be usable.
>
> For the tap driver, I always note this... IT SHOULD BE SEPARATE MSI
> and SEPARATE PROJECT.
> There should be absolutely no dependency between openvpn release cycle
> and tap release cycle.
> It is just like wireshark and libpcap projects.
> OpenVPN installer can embed the tap msi and run it during installation.
> When tap installed, it should register its version in registry key, so
> openvpn may read it in order to connect (currently it is done
> hardcoded within openvpn).
>
> The TAP driver should be built and signed using Microsoft toolchain,
> there is no problem in that. There is almost a single developer for
> the tap driver..
> The usermode components may be signed on Linux using the
> osslsigncode[3], so actual signing is not an issue, if this is desired
> I can submit a patch for "make install" to sign, as I do in other
> projects.
>
> Most (99%) users are interested in building custom user mode component
> only, so there is no sense in keeping the tap driver as dependency
> (build and sign).
>
> Regards,
> Alon.
>
> [1] https://www.opensc-project.org/build/
> [2] https://www.opensc-project.org/build/browser
> [3] http://sourceforge.net/projects/osslsigncode/
>
> 2011/11/24 Samuli Seppänen 
>>
>> Hi,
>>
>> We're having an IRC meeting today, starting at 18:00 UTC on
>> #openvpn-de...@irc.freenode.net. Current topic list is here:
>>
>> 
>>
>> If you have any other things you'd like to bring up, respond to this
>> mail, send me mail privately or add them to the list yourself.
>>
>> In case you can't attend the meeting, please feel free to make comments
>> on the topics by responding to this email or to the summary email sent
>> after the meeting.
>>
>> NOTE: It's required to use a registered Freenode IRC nickname to join
>> #openvpn-devel - look here for details:
>>
>> 
>>
>> --
>> Samuli Seppänen
>> Community Manager
>> OpenVPN Technologies, Inc
>>
>> irc freenode net: mattock
>>
>> --
>> All the data continuously generated in your IT infrastructure
>> contains a definitive record of customers, application performance,
>> security threats, fraudulent activity, and more. Splunk takes this
>> data and makes sense of it. IT sense. And common sense.
>> http://p.sf.net/sfu/splunk-novd2d
>> ___
>> Openvpn-devel mailing list
>> Openvpn-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/openvpn-devel
>

Re: [Openvpn-devel] Topics for today's meeting

2011-11-24 Thread Adriaan de Jong 
Just to put in my 2cents on the build options: there is a tool that supports 
all of those environments (gmake, cygwin, mingw, nmake, visual studio, eclipse, 
), and that's CMake. It's widely used, and has a pretty good track record. 
It can also support automated test environments and packaging.

It has one major disadvantage: the current build system would need to be 
converted from an autoconf-based to a new CMake-based system, together with all 
of the knowledge contained within it. Further, there is less knowledge of CMake 
than autoconf within the OpenVPN community.

Disclaimer: I'm not trying to start a holy war here, I know every system has 
its own advantages and drawbacks. I just want to get the option on the table 
:). I've had some positive experience with CMake, through PolarSSL and some 
projects at work. I'll try to make it to the meeting this evening for the 
discussion.

Kind Regards,

Adriaan

> -Original Message-
> From: Samuli Seppänen [mailto:sam...@openvpn.net]
> Sent: donderdag 24 november 2011 9:48
> To: openvpn-devel@lists.sourceforge.net
> Subject: [Openvpn-devel] Topics for today's meeting
> 
> Hi,
> 
> We're having an IRC meeting today, starting at 18:00 UTC on #openvpn-
> de...@irc.freenode.net. Current topic list is here:
> 
> 
> 
> If you have any other things you'd like to bring up, respond to this
> mail, send me mail privately or add them to the list yourself.
> 
> In case you can't attend the meeting, please feel free to make comments
> on the topics by responding to this email or to the summary email sent
> after the meeting.
> 
> NOTE: It's required to use a registered Freenode IRC nickname to join
> #openvpn-devel - look here for details:
> 
>  nnel>
> 
> --
> Samuli Seppänen
> Community Manager
> OpenVPN Technologies, Inc
> 
> irc freenode net: mattock
> 
> ---
> ---
> All the data continuously generated in your IT infrastructure contains
> a definitive record of customers, application performance, security
> threats, fraudulent activity, and more. Splunk takes this data and
> makes sense of it. IT sense. And common sense.
> http://p.sf.net/sfu/splunk-novd2d
> ___
> Openvpn-devel mailing list
> Openvpn-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/openvpn-devel

Re: [Openvpn-devel] Topics for today's meeting

2011-11-24 Thread Alon Bar-Lev 
Hello,

I won't participate in sync meeting don't have the time.
Anyway, for windows build.
I already provide binaries for OpenVPN using mingw-w64 project, and it
works fine!
I use mingw-w64 for both win32 and win64 binaries, much better than
old mingw project, as mingw-w64 is maintained!
You can see my build system at [1][2].
So mingw cross compile is supported. I would have re-written the
openvpn autoconf script to clean it up and make it more standard, but
current is enough to be usable.

msys can be used on Windows to build not sure it worth the effort...
mingw can be used with -mno-cygwin parameter, but from my experience
the toolchain in cygwin are way too old to be usable.

For the tap driver, I always note this... IT SHOULD BE SEPARATE MSI
and SEPARATE PROJECT.
There should be absolutely no dependency between openvpn release cycle
and tap release cycle.
It is just like wireshark and libpcap projects.
OpenVPN installer can embed the tap msi and run it during installation.
When tap installed, it should register its version in registry key, so
openvpn may read it in order to connect (currently it is done
hardcoded within openvpn).

The TAP driver should be built and signed using Microsoft toolchain,
there is no problem in that. There is almost a single developer for
the tap driver..
The usermode components may be signed on Linux using the
osslsigncode[3], so actual signing is not an issue, if this is desired
I can submit a patch for "make install" to sign, as I do in other
projects.

Most (99%) users are interested in building custom user mode component
only, so there is no sense in keeping the tap driver as dependency
(build and sign).

Regards,
Alon.

[1] https://www.opensc-project.org/build/
[2] https://www.opensc-project.org/build/browser
[3] http://sourceforge.net/projects/osslsigncode/

2011/11/24 Samuli Seppänen 
>
> Hi,
>
> We're having an IRC meeting today, starting at 18:00 UTC on
> #openvpn-de...@irc.freenode.net. Current topic list is here:
>
> 
>
> If you have any other things you'd like to bring up, respond to this
> mail, send me mail privately or add them to the list yourself.
>
> In case you can't attend the meeting, please feel free to make comments
> on the topics by responding to this email or to the summary email sent
> after the meeting.
>
> NOTE: It's required to use a registered Freenode IRC nickname to join
> #openvpn-devel - look here for details:
>
> 
>
> --
> Samuli Seppänen
> Community Manager
> OpenVPN Technologies, Inc
>
> irc freenode net: mattock
>
> --
> All the data continuously generated in your IT infrastructure
> contains a definitive record of customers, application performance,
> security threats, fraudulent activity, and more. Splunk takes this
> data and makes sense of it. IT sense. And common sense.
> http://p.sf.net/sfu/splunk-novd2d
> ___
> Openvpn-devel mailing list
> Openvpn-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/openvpn-devel

Re: [Openvpn-devel] Topics for today's meeting

2010-06-03 Thread reg9009 

 Am 03.06.2010 14:06, schrieb Samuli Seppänen:

Hi,

Here are some topics for today's meeting (18:00 UTC,
#openvpn-de...@irc.freenode.net).



If you have any other things you'd like to bring up, add them to the
list or send them to me.


Hi all,

I'd like to raise an additional topic, state/instance synchronization 
between OpenVPN instances (transparent failover option).


Regards,
Sebastian