-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 22/02/12 17:46, David Sommerseth wrote:
> On 22/02/12 17:13, Alon Bar-Lev wrote:
>> Dear project managers. I need a decision regarding the minimum
>> supported openssl.
>
> I'd say we support these libraries and tools as the oldest supported:
>
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 22/02/12 17:13, Alon Bar-Lev wrote:
> Dear project managers. I need a decision regarding the minimum
> supported openssl.
I'd say we support these libraries and tools as the oldest supported:
> =autoconf-2.59 =automake-1.9 =libtool-1.5.22 =lzo-2.0
Dear project managers.
I need a decision regarding the minimum supported openssl.
Hi,
On Tue, Feb 21, 2012 at 09:20:50PM +0200, Samuli Seppänen wrote:
> Also, ecrist publishes source tarballs every couple of weeks already...
> couldn't these old autotools users use those and still get failrly
> recent OpenVPN versions on their boxes?
Exactly.
You need autotools if you want to
Hi,
On Tue, Feb 21, 2012 at 04:56:37PM +0100, David Sommerseth wrote:
> There might be similar restrictions related to autoconf/automake tools
> too. As James has some automation for the Access Server builds for those
> supported platforms, we must be sure we don't break that for him. From
> wha
Hi,
On Tue, Feb 21, 2012 at 05:15:22PM +0200, Alon Bar-Lev wrote:
> OpenVPN supports minimum openssl version of 0.9.6, while this version
> is unsupported by upstream and probably a security risk.
>
> What would be a suitable minimum version to support?
>
> I think that 0.9.8 is the one.
FreeBS
2012/2/21 Samuli Seppänen :
> I would be inclined to focus on cutting down complexity as much as
> possible. I think the best way to gauge real need for old autotools is
> to scrap support for it. We can always fix things afterwards, if
> necessary. I can ask James' opinion if he does not step in s
> On Tue, Feb 21, 2012 at 7:51 PM, David Sommerseth
> wrote:
>>> No there is none. Unlike other dependencies autotools dependencies are
>>> of development machine. You should create tarball on newer machine
>>> then compile it on the target platform. Target platform may not have
>>> autotools ins
On Tue, Feb 21, 2012 at 7:51 PM, David Sommerseth
wrote:
>> No there is none. Unlike other dependencies autotools dependencies are
>> of development machine. You should create tarball on newer machine
>> then compile it on the target platform. Target platform may not have
>> autotools installed at
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 21/02/12 17:12, Alon Bar-Lev wrote:
> On Tue, Feb 21, 2012 at 5:56 PM, David Sommerseth
> wrote:
>> There might be similar restrictions related to autoconf/automake
>> tools too. As James has some automation for the Access Server
>> builds for th
On Tue, Feb 21, 2012 at 5:56 PM, David Sommerseth
wrote:
> There might be similar restrictions related to autoconf/automake tools
> too. As James has some automation for the Access Server builds for those
> supported platforms, we must be sure we don't break that for him. From
> what I see, on a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 21/02/12 16:15, Alon Bar-Lev wrote:
> Hello,
>
> OpenVPN supports minimum openssl version of 0.9.6, while this version
> is unsupported by upstream and probably a security risk.
>
> What would be a suitable minimum version to support?
>
> I thin
- Mail original -
> De: "Alon Bar-Lev"
> À: "openvpn-devel@lists.sourceforge.net"
> Envoyé: Mardi 21 Février 2012 16:15:22
> Objet: [Openvpn-devel] [RFC] openssl minimum supported version
>
> Hello,
>
> OpenVPN supports minimum opens
Alon Bar-Lev wrote:
> Hello,
>
> OpenVPN supports minimum openssl version of 0.9.6, while this version
> is unsupported by upstream and probably a security risk.
>
> What would be a suitable minimum version to support?
>
> I think that 0.9.8 is the one.
>
EL5 and most SuSE distro's still use 0.
Hello,
OpenVPN supports minimum openssl version of 0.9.6, while this version
is unsupported by upstream and probably a security risk.
What would be a suitable minimum version to support?
I think that 0.9.8 is the one.
Regards,
Alon.
15 matches
Mail list logo