Just a recommendation, but I wouldn't necessarily consider the two proposals
alternatives. The only interesting thing going on here is an implementation of
open_tun that creates utun devices. The rest is just wiring. Even open_tun
isn't really subtle or complex, merely a bit arcane. I suspect th
Hi,
On Mon, Jun 17, 2013 at 09:32:35AM +0200, Joachim Schipper wrote:
> Again, thanks for the patch! I'm no contributor, but I do think it's really
> cool.
By helping review crypto related code, you are contributing in quite
important ways :-)
"Contributor" does not require "write code" or "han
Hi,
On Mon, Jun 17, 2013 at 11:33:54AM -0400, Jonathan K. Bullard wrote:
> I have a slight preference forArne's patch, which doesn't introduce yet
> another new OpenVPN option.
Without having compared the code itself, I second that argument. No more
super-special-case options (which depend on #i
On Mon, Jun 17, 2013 at 05:36:23PM +0200, Gert Doering wrote:
> Hi,
>
> On Mon, Jun 17, 2013 at 04:36:44PM +0200, Alberto Gonzalez Iniesta wrote:
> > Seems like "cmsg_len" went nuts...
>
> Seems your compiler grew too much smarts and optimized that bug to death :-)
>
> > Again, only happens with
Hi,
On Mon, Jun 17, 2013 at 04:36:44PM +0200, Alberto Gonzalez Iniesta wrote:
> Seems like "cmsg_len" went nuts...
Seems your compiler grew too much smarts and optimized that bug to death :-)
> Again, only happens with multihome, if that helps...
That code path is only used for multihome. Bugf
On Sun, Jun 16, 2013 at 5:14 PM, Arne Schwabe wrote:
>
> I think using utun as default at least for -master and 2.4rc candidates is
> a good way to get the feature tested. I hope there is time in the next
> OpenVPN developer IRC meeting to decide if my or your patch should be
> included.
I won'
On Mon, Jun 17, 2013 at 04:05:18PM +0200, Alberto Gonzalez Iniesta wrote:
> On Mon, Jun 17, 2013 at 01:51:13PM +0200, Gert Doering wrote:
> > Hi,
> >
> > On Mon, Jun 17, 2013 at 01:00:03PM +0200, Alberto Gonzalez Iniesta wrote:
> > > I applied the fix for CVE-2013-2061 [0] to Debian's stable versi
On Mon, Jun 17, 2013 at 01:51:13PM +0200, Gert Doering wrote:
> Hi,
>
> On Mon, Jun 17, 2013 at 01:00:03PM +0200, Alberto Gonzalez Iniesta wrote:
> > I applied the fix for CVE-2013-2061 [0] to Debian's stable version of
> > openvpn (2.2.1) [1]. When the new package was sent to the mirrors I got
>
Hi,
On Mon, Jun 17, 2013 at 01:00:03PM +0200, Alberto Gonzalez Iniesta wrote:
> I applied the fix for CVE-2013-2061 [0] to Debian's stable version of
> openvpn (2.2.1) [1]. When the new package was sent to the mirrors I got
> a couple of reports of broken VPNs [2]. After some testing I think the
>
Hi,
I applied the fix for CVE-2013-2061 [0] to Debian's stable version of
openvpn (2.2.1) [1]. When the new package was sent to the mirrors I got
a couple of reports of broken VPNs [2]. After some testing I think the
problem arises with the use of "multihome" option. The server daemon
starts to lo
On 06/14/2013 09:53 PM, James Yonan wrote:
> To get the adaptive versioning behavior in OpenSSL, you have to use
> SSLv23_server_method() or SSLv23_client_method() and then explicitly
> disable the versions you don't want to consider, i.e. SSL_OP_NO_SSLv2,
> SSL_OP_NO_SSLv3, SSL_OP_NO_TLSv1, SSL
> -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 al.)
>
> I wrote a patch to add AEAD cipher modes to OpenVPN. This is
12 matches
Mail list logo
