Hi,
On Thu, Apr 13, 2017 at 04:23:56AM +1000, Steven McDonald wrote:
> For example, OpenBSD does have pkg-config for libssl, but hasn't
> updated it since LibreSSL was forked:
>
> $ pkg-config --modversion libssl
> 1.0.0
I think LibreSSL needs to just die in flames...
Their approach of "we
Hi,
On Wed, 12 Apr 2017 08:24:37 +0200
Gert Doering wrote:
> While this *looks* harmless, it has non-obvious side effects - from
> what I observe, it breaks compilation on all platforms that do not
> have pkg_config for OpenSSL, which was not a requirement earlier (and
> there even was a comment
This allows the user to specify what certificate crypto algorithms to
support. The supported profiles are 'preferred' (default), 'legacy' and
'suiteb', as discussed in <84590a17-1c48-9df2-c48e-4160750b2...@fox-it.com>
(https://www.mail-archive.com/openvpn-devel@lists.sourceforge.net/msg14214.html)
Hi,
On 11-04-17 23:56, David Sommerseth wrote:
> On 11/04/17 23:20, Steffan Karger wrote:
>> On 11-04-17 19:31, David Sommerseth wrote:
>>> As RHEL 5 has reached EOL, we no longer need to support OpenSSL v0.9.8.
>>> This also makes it possible to remove a few workaronds which was
>>> needed earlie
On 12/04/17 06:58, Simon Matter wrote:
>> Hi,
>>
>> On 11-04-17 19:31, David Sommerseth wrote:
>>> As RHEL 5 has reached EOL, we no longer need to support OpenSSL v0.9.8.
>>> This also makes it possible to remove a few workaronds which was
>>> needed earlier, as well as some left overs from v0.9.6.
On 12/04/17 03:06, Matthias Andree wrote:
> Am 11.04.2017 um 23:56 schrieb David Sommerseth:
>> On 11/04/17 23:20, Steffan Karger wrote:
>>> For release/2.4: I wonder whether we need to keep 0.9.8 support, as
>>> SLES11 still ships with 0.9.8h, and has general support until 31 Mar 2019.
>> While it
