Re: [Openvpn-devel] OpenVPN Versioning

2013-06-18 Thread Joachim Schipper
From: James Yonan : > On 14/06/2013 02:47, Joachim Schipper wrote: > >>From James Yonan : > >> TLS Protocol > >> > >> > >> Since day 1, OpenVPN has used TLS 1.0 as a control channel and key > >> exchange mechanism. But now we have TLS 1.1 and 1.2, each of which > >> addresses signific

Re: [Openvpn-devel] Native OS X tunnels

2013-06-18 Thread Gert Doering
Hi, On Mon, Jun 17, 2013 at 11:51:53AM -0700, Peter Sagerson wrote: > Just a recommendation, but I wouldn't necessarily consider the two > proposals alternatives. I agree - the basic functionality is the same, just some of the surrounding details are different. As I said, I need to closely loo

Re: [Openvpn-devel] Adding support for AEAD cipher modes (AES-GCM, et al.)

2013-06-18 Thread Joachim Schipper
Joachim Schipper wrote [I'm continuing my own message here]: > > -Original Message- > > From: Kenny Root [mailto:ke...@the-b.org] > > Sent: dinsdag 4 juni 2013 2:15 > > To: openvpn-devel@lists.sourceforge.net > > Subject: [Openvpn-devel] Adding support for AEAD cipher modes > > (AES-GCM, et

[Openvpn-devel] [Patch v2] Add support of utun devices under Mac OS X

2013-06-18 Thread Arne Schwabe
Mac OS X 10.7+ natively supports tun devices (called utun). The "standard" utun.ko driver is sometimes problematic (e.g. VmWare Fusion 5 and tun.ko do not work together). When OpenVPN is compiled with utun support it will if no dev-node is given first try to use utun and if that is not availabl