From: Gert Doering g...@greenie.muc.de
Sent: Tue Jul 29 07:41:58 CEST 2014
To: Lisa Minogue lmino...@mail.be
Subject: Re: [Openvpn-users] OpenVPN binary package (2.3.4) for OpenBSD?
Hi,
On Tue, Jul 29, 2014 at 04:08:07AM +0200, Lisa Minogue wrote:
Could someone tell me where I can
Hi,
On Tue, Jul 29, 2014 at 11:27:27AM +0200, Lisa Minogue wrote:
Thanks Gert for your reply.
Suppose the maintainer for OpenVPN port at OpenBSD says that the
current OpenVPN 2.3.4 version will only be available for OpenBSD
5.6 (scheduled for release in November 2014), what should users of
From: Gert Doering g...@greenie.muc.de
Sent: Tue Jul 29 11:54:37 CEST 2014
To: Lisa Minogue lmino...@mail.be
Subject: Re: [Openvpn-users] OpenVPN binary package (2.3.4) for OpenBSD?
Compile it yourself? OpenVPN should compile nicely and without
Hi,
On Tue, Jul 29, 2014 at 01:30:35PM +0200, Lisa Minogue wrote:
Compile it yourself? OpenVPN should compile nicely and without issues on
OpenBSD (and compiling OpenVPN on unix versions is straightforward).
Is there any guide on how to compile OpenVPN on *nix operating systems? I
have
Hi,
From: Gert Doering g...@greenie.muc.de
Sent: Tue Jul 29 13:53:27 CEST 2014
To: Lisa Minogue lmino...@mail.be
Subject: Re: [Openvpn-users] OpenVPN binary package (2.3.4) for OpenBSD?
Well, in the package itself, there are two files called
Hi Samuli
It's nice to hear from you.
Gert has helped to clarify my doubts. That's nice of him :)
Maybe there is no OpenBSD binary package for OpenVPN 2.3.4? In that case you
need to compile 2.3.4 from the sources available on openvpn.net.
Yes, Gert did advise me to compile it using the
Hi,
On Tue, Jul 29, 2014 at 03:08:25PM +0200, Lisa Minogue wrote:
[seriously, if it's so easy as you seem to make it out to be,
why doesn't the maintainer of OpenVPN for OpenBSD compile and upload
version 2.3.4 sooner? What's holding him back?
Ask them. Maybe they are just humans, need to
Hi
2.3.2 - 2.3.4 has no significant security impact (if I remember correctly),
it's just the provided *windows* binaries have, because they bundle OpenSSL
and that one was vulnerable. So from a security PoV, it's ok to stick to
2.3.2, as any version change could bring in new bugs...
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi
2.3.2 - 2.3.4 has no significant security impact (if I remember
correctly), it's just the provided *windows* binaries have, because they
bundle OpenSSL and that one was vulnerable. So from a security PoV,
it's ok to stick to
2.3.2, as any
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Samuli
I can't confirm that 2.3.2 and 2.3.4 are equal from a security point
of view, because as Gert said, any version change could bring in new
[security] bugs :).
Please clarify for me and possibly for those who are interested in
this
Hi,
On Tue, Jul 29, 2014 at 06:00:48PM +0200, Lisa Minogue wrote:
I can't confirm that 2.3.2 and 2.3.4 are equal from a security point of
view, because as Gert said, any version change could bring in new
[security] bugs :).
Please clarify for me and possibly for those who are
Hi Gert,
Those are bugfixes, but not *security* fixes. Like, some seldom-used
functionality not working right on some of the supported OSes (like the
route-gateway stuff, which only affects *client* use on some of the BSDs).
You wrote: which only affects client use on some of the BSDs.
Hi,
On Tue, Jul 29, 2014 at 11:03:46PM +0200, Lisa Minogue wrote:
Those are bugfixes, but not *security* fixes. Like, some seldom-used
functionality not working right on some of the supported OSes (like the
route-gateway stuff, which only affects *client* use on some of the BSDs).
You
13 matches
Mail list logo