On 01.11.2016 23:47, David Sommerseth wrote:
>
> I'm splitting of the originating thread to a new one, to refocus the
> discussion.
>
> On 01/11/16 15:56, Samuli Seppänen wrote:
> > Il 01/11/2016 16:05, David Sommerseth ha scritto:
> >> [...snip...]
> >>
> I still think the timeline "end of 20
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I'm splitting of the originating thread to a new one, to refocus the
discussion.
On 01/11/16 15:56, Samuli Seppänen wrote:
> Il 01/11/2016 16:05, David Sommerseth ha scritto:
>> [...snip...]
>>
I still think the timeline "end of 2016" should be
ACK.
Your patch has been applied to the master and release/2.3 branch.
commit beaa6564a7ce3e48473a8bde7b4f9291df490d62 (master)
commit 28778220dd50fd68f0f81cbcc1c73fdd16f04be8 (release/2.3)
Author: David Sommerseth
Date: Tue Nov 1 14:38:09 2016 +0100
man: Improve the --keepalive section
As reported by debbie10t on the openvpn-devel list (Message-ID:
<326b8ff7-39a6-1974-c0b0-82fd2abdc...@gmail.com>), an NCP client will
attempt to reconnect with the previously pushed cipher, instead of the
cipher from the config file, after a sigusr1 restart. This can be a
problem when the server i
Hi,
Il 01/11/2016 16:05, David Sommerseth ha scritto:
> On 01/11/16 13:20, Samuli Seppänen wrote:
>> Hi,
>>
>> Il 01/11/2016 13:10, Gert Doering ha scritto:
>>> Hi,
>>>
>>> On Mon, Oct 31, 2016 at 11:55:08PM +0100, David Sommerseth wrote:
How long will users be willing to wait? I'd be really
On 01/11/16 13:20, Samuli Seppänen wrote:
> Hi,
>
> Il 01/11/2016 13:10, Gert Doering ha scritto:
>> Hi,
>>
>> On Mon, Oct 31, 2016 at 11:55:08PM +0100, David Sommerseth wrote:
>>> How long will users be willing to wait? I'd be really surprised if 2.4
>>> is out the door before Christmas 2016. W
Just minor clarifications and corrections of the --keepalive option.
v2 - Changed from ps/pto to interval/timeout
- Rephrased the server-side timeout doubling parapgraph
Signed-off-by: David Sommerseth
---
doc/openvpn.8 | 31 ---
1 file changed, 20 insertions(
Hi,
On Tue, Nov 01, 2016 at 01:28:16PM +0100, Steffan Karger wrote:
> > But I'm very open for other suggestions; I don't care about the bikeshed
> > colour as long as it is at least a slight improvement of what we have today.
>
> "Thou shell never waste an opportunity to bikeshed."
Be our guest
On 01-11-16 13:19, David Sommerseth wrote:
> On 01/11/16 12:28, Gert Doering wrote:
>> On Mon, Oct 31, 2016 at 03:01:28PM +0100, David Sommerseth wrote:
>>> -.B \-\-keepalive n m
>>> +.B \-\-keepalive ps pto
>>
>> What does "ps" stand for? I find this not much clearer than "n"...
>
>> "pto" sound
Hi,
Il 01/11/2016 13:10, Gert Doering ha scritto:
> Hi,
>
> On Mon, Oct 31, 2016 at 11:55:08PM +0100, David Sommerseth wrote:
>> How long will users be willing to wait? I'd be really surprised if 2.4
>> is out the door before Christmas 2016. When also considering we've said
>> that 2.4_alpha was
On 01/11/16 12:28, Gert Doering wrote:
> Hi,
>
> On Mon, Oct 31, 2016 at 03:01:28PM +0100, David Sommerseth wrote:
>> -.B \-\-keepalive n m
>> +.B \-\-keepalive ps pto
>
> What does "ps" stand for? I find this not much clearer than "n"...
> "pto" sounds like "ping time out", which I find halfwa
Hi,
On Mon, Oct 31, 2016 at 03:01:28PM +0100, David Sommerseth wrote:
> -.B \-\-keepalive n m
> +.B \-\-keepalive ps pto
What does "ps" stand for? I find this not much clearer than "n"...
"pto" sounds like "ping time out", which I find halfway understandable.
Maybe make the first argument "t"
Hi,
On Mon, Oct 31, 2016 at 11:55:08PM +0100, David Sommerseth wrote:
> How long will users be willing to wait? I'd be really surprised if 2.4
> is out the door before Christmas 2016. When also considering we've said
> that 2.4_alpha was soon ready for about 1 year or so before it really
> got r
Il 01/11/2016 00:55, David Sommerseth ha scritto:
> On 31/10/16 23:25, debbie10t wrote:
>>
>>
>> On 31/10/16 21:30, David Sommerseth wrote:
>>
>>> So let's try to aim at pleasing the end user than being picky about the
>>> wording of a track ticket. Because most users will be thankful for a
>>> re
ACK, thanks.
Build tested with default options, --disable-crypto, --disable-management,
and --disable-server. All compile fine and pass whatever test can still
be run (not much for --disable-crypto today).
Your patch has been applied to the master branch.
commit 51d4d1543a64158cc24f176a8d45e51c
15 matches
Mail list logo
