>> I considered that (modulo the sleep 60) and wrote the code to do the
>> configure check, but then thought that a not-suppressible warning in the
>> logs would be sufficient. I still think it is, but don't mind re-adding
>> it to configure.ac if you prefer that.
>
> As an OpenBSD developer an
On Sun, Mar 04 2018, Steffan Karger wrote:
> Hi,
>
> On 04-03-18 10:08, Gert Doering wrote:
>> On Thu, Mar 01, 2018 at 12:11:23AM +0100, Steffan Karger wrote:
>>> As discussed in the community meeting of 13-12-2017, we should warn our
>>> users that LibreSSL is not officially supported. We expect
Hi,
On 04-03-18 10:08, Gert Doering wrote:
> On Thu, Mar 01, 2018 at 12:11:23AM +0100, Steffan Karger wrote:
>> As discussed in the community meeting of 13-12-2017, we should warn our
>> users that LibreSSL is not officially supported. We expect that it
>> currently works, but it might suddenly b
Hi,
On Thu, Mar 01, 2018 at 12:11:23AM +0100, Steffan Karger wrote:
> As discussed in the community meeting of 13-12-2017, we should warn our
> users that LibreSSL is not officially supported. We expect that it
> currently works, but it might suddenly break or we might decide to no
> longer build
[resending because the list rejected my mail from yesterday...]
On 1 March 2018 at 00:11, Steffan Karger wrote:
> +msg(M_WARN, "WARNING: This OpenVPN was built against LibreSSL. "
> +"This might work, but is *not* supported and can break at any time.")
Gah, this of course needs a ; a
As discussed in the community meeting of 13-12-2017, we should warn our
users that LibreSSL is not officially supported. We expect that it
currently works, but it might suddenly break or we might decide to no
longer build against LibreSSL in the future.
There seem to be ongoing efforts to make Li
