Re: [Openvpn-devel] [PATCH 9/9] Add detailed man page section to setup a OpenVPN setup with peer-fingerprint

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hi, missed another one .. ‐‐‐ Original Message ‐‐‐ On Thursday, 20 May 2021 01:13, tincantech wrote: > Hi, > > just FYI > > I was also going to question the --tun-mtu 1400 setting but decided > that was above my pay-grade. I think it is p

Re: [Openvpn-devel] [PATCH 9/9] Add detailed man page section to setup a OpenVPN setup with peer-fingerprint

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hi, just FYI I was also going to question the --tun-mtu 1400 setting but decided that was above my pay-grade. I think it is probably a good long-term decision that will probably invade some of those less respectable blogs and be a good thing over-

Re: [Openvpn-devel] [PATCH 9/9] Add detailed man page section to setup a OpenVPN setup with peer-fingerprint

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hi, ‐‐‐ Original Message ‐‐‐ On Thursday, 20 May 2021 00:36, Arne Schwabe wrote: > > I just want this to be verified because the manual reads that: > > udp6 will force only udp on IPv6, at least that is how I read it. > > Not on the server

Re: [Openvpn-devel] [PATCH 9/9] Add detailed man page section to setup a OpenVPN setup with peer-fingerprint

> I just want this to be verified because the manual reads that: > udp6 will force only udp on IPv6, at least that is how I read it. Not on the server side. It is one of the quirks that we need to fix at some point. See the ipv6only option of --bind for more details > >> + >> +# The ip add

Re: [Openvpn-devel] Summary of the community meeting (19th May 2021)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hi, ‐‐‐ Original Message ‐‐‐ On Wednesday, 19 May 2021 14:31, Samuli Seppänen wrote: > Hi, > > Here's the summary of the IRC meeting. > > > > COMMUNITY MEETING > > Place: #openvpn-meeting on irc

[Openvpn-devel] [PATCH applied] Re: Ignore leading whitespace and comment lines for peer-fingerprint.

Patch has been applied to the master branch. commit de78371ab83f7d533d65ccf966684e31b57d953f Author: Gert Doering Date: Wed May 19 15:34:15 2021 +0200 Ignore leading whitespace and comment lines for peer-fingerprint. Signed-off-by: Gert Doering Acked-by: Selva Nair Messag

Re: [Openvpn-devel] [PATCH v3] Ignore leading whitespace and comment lines for peer-fingerprint.

Hi On Wed, May 19, 2021 at 9:35 AM Gert Doering wrote: > > Inline peer-fingerprint blocks can benefit from a bit of structuring > by indentation or by putting comments ("# this is Alice's key"). > > v2: accept ';' and '#' as comment delimiter. Fix tab-indent. > v3: we want == > > Signed-off-by:

[Openvpn-devel] [PATCH v3] Ignore leading whitespace and comment lines for peer-fingerprint.

Inline peer-fingerprint blocks can benefit from a bit of structuring by indentation or by putting comments ("# this is Alice's key"). v2: accept ';' and '#' as comment delimiter. Fix tab-indent. v3: we want == Signed-off-by: Gert Doering --- src/openvpn/options.c | 9 +++-- 1 file changed,

[Openvpn-devel] Summary of the community meeting (19th May 2021)

Hi, Here's the summary of the IRC meeting. --- COMMUNITY MEETING Place: #openvpn-meeting on irc.freenode.net Date: Wed 19th May 2021 Time: 14:00 CET (12:00 UTC) Planned meeting topics for this meeting were here: Your local meeti

Re: [Openvpn-devel] [PATCH v2] Ignore leading whitespace and comment lines for peer-fingerprint.

Hi, On Wed, May 19, 2021 at 1:58 AM Gert Doering wrote: > > Inline peer-fingerprint blocks can benefit from a bit of structuring > by indentation or by putting comments ("# this is Alice's key"). > > v2: accept ';' and '#' as comment delimiter. Fix tab-indent. > > Signed-off-by: Gert Doering >

[Openvpn-devel] [PATCH applied] Re: openvpnmsica: properly schedule reboot in the end of installation

Acked-by: Gert Doering While I do not understand all the intricacies of MSI and WiX, the fact that Simon has approved the corresponding openvpn-build PR 215 tells me that this one also should go forward. I have stared a bit at the code, and it seems to be doing what the commit says :-) I have n