On 28/03/17 14:47, Gert Doering wrote:
> Hi,
>
> On Tue, Mar 28, 2017 at 02:35:59PM +0200, David Sommerseth wrote:
>> On 28/03/17 14:21, Gert Doering wrote:
>>> On Tue, Mar 28, 2017 at 02:11:26PM +0200, David Sommerseth wrote:
> That's great! This way, 2.4 does not have to change it's
On 28/03/2017 17:11, debbie10t wrote:
>>
>> Agreed: a simple Deprecation page on the wiki linking to changes.rst
>>
>> The wiki page *could* also be updated from time to time to provide
>> specific warnings of important changes like deprecating --ns-cert-type
>> as it has been identified that it
On 28/03/17 15:05, debbie10t wrote:
>
>
> On 28/03/17 14:41, Steffan Karger wrote:
>> On 28-03-17 15:31, Samuli Seppänen wrote:
>>> On 28/03/2017 16:08, Steffan Karger wrote:
On 28-03-17 15:02, debbie10t wrote:
> On 28/03/17 13:47, Gert Doering wrote:
>> We need to communicate
On 28/03/17 14:41, Steffan Karger wrote:
> On 28-03-17 15:31, Samuli Seppänen wrote:
>> On 28/03/2017 16:08, Steffan Karger wrote:
>>> On 28-03-17 15:02, debbie10t wrote:
On 28/03/17 13:47, Gert Doering wrote:
> We need to communicate better what might affect users in new versions, so
On 28-03-17 15:31, Samuli Seppänen wrote:
> On 28/03/2017 16:08, Steffan Karger wrote:
>> On 28-03-17 15:02, debbie10t wrote:
>>> On 28/03/17 13:47, Gert Doering wrote:
We need to communicate better what might affect users in new versions, so
they can test and complain/adjust in time
On 28/03/2017 16:08, Steffan Karger wrote:
> On 28-03-17 15:02, debbie10t wrote:
>> On 28/03/17 13:47, Gert Doering wrote:
>>> We need to communicate better what might affect users in new versions, so
>>> they can test and complain/adjust in time (like, the stricter CRL handling
>>> in 2.4, and -
On 28/03/2017 16:02, debbie10t wrote:
>
>
> On 28/03/17 13:47, Gert Doering wrote:
>
>> We need to communicate better what might affect users in new versions, so
>> they can test and complain/adjust in time (like, the stricter CRL handling
>> in 2.4, and - obviously - the --tls-remote bit)
>
>
On 28-03-17 15:02, debbie10t wrote:
> On 28/03/17 13:47, Gert Doering wrote:
>> We need to communicate better what might affect users in new versions, so
>> they can test and complain/adjust in time (like, the stricter CRL handling
>> in 2.4, and - obviously - the --tls-remote bit)
>
>
On 28/03/17 13:47, Gert Doering wrote:
> We need to communicate better what might affect users in new versions, so
> they can test and complain/adjust in time (like, the stricter CRL handling
> in 2.4, and - obviously - the --tls-remote bit)
Suggestion: A Wiki Page detailing deprecation plans
Hi,
On Tue, Mar 28, 2017 at 02:35:59PM +0200, David Sommerseth wrote:
> On 28/03/17 14:21, Gert Doering wrote:
> > On Tue, Mar 28, 2017 at 02:11:26PM +0200, David Sommerseth wrote:
> >>> That's great! This way, 2.4 does not have to change it's behaviour.
> >>> Still, I think it makes sense to
On 28/03/17 14:21, Gert Doering wrote:
> Hi,
>
> On Tue, Mar 28, 2017 at 02:11:26PM +0200, David Sommerseth wrote:
>>> That's great! This way, 2.4 does not have to change it's behaviour.
>>> Still, I think it makes sense to deprecate --ns-cert-type, and remove it
>>> in favour or
Hi,
On Tue, Mar 28, 2017 at 02:11:26PM +0200, David Sommerseth wrote:
> > That's great! This way, 2.4 does not have to change it's behaviour.
> > Still, I think it makes sense to deprecate --ns-cert-type, and remove it
> > in favour or --remote-cert-tls in openvpn 2.5.
>
> Based on the feedback
On 28/03/17 10:39, Steffan Karger wrote:
> Hi,
>
> On 28-03-17 10:33, Emmanuel Deloget wrote:
>> I should be able to push a new version of the remaining patches in the
>> foreseeable future (let's say today or tomorrow, because I will be
>> unavailable at the end of this week).
>>
>> I found a
Hi,
On 28-03-17 10:33, Emmanuel Deloget wrote:
> I should be able to push a new version of the remaining patches in the
> foreseeable future (let's say today or tomorrow, because I will be
> unavailable at the end of this week).
>
> I found a solution to overcome the big X509_check_purpose()
Hi,
On Mon, Mar 27, 2017 at 8:35 PM, Gert Doering wrote:
> Hi,
>
> On Mon, Mar 27, 2017 at 11:25:50AM -0700, PGNet Dev wrote:
> > noting
> >
> > openvpn fails to build with openssl 1.1
> > https://community.openvpn.net/openvpn/ticket/759
>
> Guess why
Hi,
On Mon, Mar 27, 2017 at 11:25:50AM -0700, PGNet Dev wrote:
> noting
>
> openvpn fails to build with openssl 1.1
> https://community.openvpn.net/openvpn/ticket/759
Guess why that ticket is still open?
> [Openvpn-devel] [RFC PATCH v1 00/15] Add support for OpenSSL
fyi,
noting
openvpn fails to build with openssl 1.1
https://community.openvpn.net/openvpn/ticket/759
[Openvpn-devel] [RFC PATCH v1 00/15] Add support for OpenSSL 1.1.x
https://www.mail-archive.com/openvpn-devel@lists.sourceforge.net/msg14075.html
17 matches
Mail list logo