-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Forwarding to openvpn-devel, as requested.
CC'ing -users FTR.
--- Original Message ---
On Tuesday, June 28th, 2022 at 02:59, Selva Nair wrote:
> Hi,
>
>
> >
> > the \\config-auto folder is only created if the 'openVPN Service' is
> > se
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi,
ref: https://forums.openvpn.net/viewtopic.php?t=34461
Food for thought..
R
-BEGIN PGP SIGNATURE-
Version: ProtonMail
wsBzBAEBCAAGBQJiv25tACEJEE+XnPZrkLidFiEECbw9RGejjXJ5xVVVT5ec
9muQuJ3+uQf8C4svn9uGUDXcjPAohtlnw0/w3WjQI1yY3cHjGTro6Kh
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi Magnus,
can you report this as an issue on github, please ?
https://github.com/OpenVPN/easy-rsa/issues
My first guess would be the version of openssl 3.0.1 is at fault.
Thanks,
Richard
Sent with Proton Mail secure email.
--- Original M
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi,
Plus one more typo.
Sent with Proton Mail secure email.
--- Original Message ---
On Thursday, October 20th, 2022 at 11:05, Arne Schwabe wrote:
> diff --git a/src/openvpn/common.h b/src/openvpn/common.h
> index b94680885..dce6fd01d
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi,
On Wednesday, 14 February 2024 at 15:22, Frank Lichtenheld
wrote:
> Meeting summary for 14 February 2024:
> * New: Easy-rsa in Windows installers
> easy-rsa has included pre-built Windows binaries for a long time. But with
> Windows 11 the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Sent with ProtonMail Secure Email.
‐‐‐ Original Message ‐‐‐
On Friday, 2 April 2021 19:35, Simon Matter wrote:
> > Commit 8fa8a17528c001a introduces "compress migrate" to move old clients
> > that have "compress" or "comp-lzo" in their
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Sent with ProtonMail Secure Email.
‐‐‐ Original Message ‐‐‐
On Saturday, 3 April 2021 01:43, tincantech via Openvpn-devel
wrote:
>
> But i believe you need to have access to both the compressed VPN data
> and the uncompres
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Sent with ProtonMail Secure Email.
‐‐‐ Original Message ‐‐‐
On Saturday, 3 April 2021 19:46, Arne Schwabe wrote:
> Using OpenVPN without P2MP support (pull, TLS) is unrealistic and
> building a binary without it is not something we real
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Before this goes any further, I doubt very much that Openvpn intends to "Remove
P2MP mode".
Sent with ProtonMail Secure Email.
‐‐‐ Original Message ‐‐‐
On Thursday, 1 April 2021 18:27, Arne Schwabe wrote:
> Am 01.04.21 um 15:13 schrieb
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi,
‐‐‐ Original Message ‐‐‐
On Friday, 9 April 2021 10:53, Arne Schwabe wrote:
>
> I am not sure how you came to that conclusion. I have written a fairly
> comprehensible documentation how NCP in 2.5 works for our manpage:
> https://git
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi,
‐‐‐ Original Message ‐‐‐
On Friday, 9 April 2021 17:28, Gert Doering wrote:
> I do not use --persist-key, but I still restart my services after fiddling
> with configs...
>
Same.
To add weight here, I would estimate 95%+ of all pos
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
hi,
I am requesting that $daemon_pid be added to the --tls-crypt-v2-verify
environment.
FTR: $daemon_pid is currently undocumented in all three manuals.
Thanks.
R
-BEGIN PGP SIGNATURE-
Version: ProtonMail
wsBzBAEBCAAGBQJggeRlACEJEE+XnPZr
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi,
‐‐‐ Original Message ‐‐‐
On Friday, 23 April 2021 07:13, Gert Doering wrote:
> Hi,
>
> On Thu, Apr 22, 2021 at 09:02:30PM +, tincantech via Openvpn-devel wrote:
>
> > I am requesting that $daemon_pid be added to
021 08:12, Antonio Quartulli a...@unstable.cc wrote:
> >
> > > Hi,
> >
> > > On 22/04/2021 23:02, tincantech via Openvpn-devel wrote:
> >
> > > > hi,
> > > > I am requesting that $daemon_pid be added to the --tls-crypt-v2-verify
> > &
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi,
‐‐‐ Original Message ‐‐‐
On Friday, 23 April 2021 08:12, Antonio Quartulli wrote:
> Hi,
>
> On 22/04/2021 23:02, tincantech via Openvpn-devel wrote:
>
> > hi,
> > I am requesting that $daemon_pid be added to t
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi,
I am requesting that daemon_pid be added to --tls-crypt-v2-verify env.
Version 2
Justification:
With the notable exception of --tls-crypt-v2-verify ..
daemon_pid provides a verified process ID to All scripts. This ensures
that scripts which ar
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi,
no complaints yet ?
Sent with ProtonMail Secure Email.
ProtonMail, as crap as googlemail.
‐‐‐ Original Message ‐‐‐
On Friday, 23 April 2021 22:16, tincantech via Openvpn-devel
wrote:
> Hi,
>
> I am requesting that daem
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Openvpn process ID (daemon_pid) provides the most secure way for
scripts to verify which process they were called by.
This patch adds daemon_poid to --tls-crypt-v2-verify environment.
Tested on Linux and Windows.
diff --git a/src/openvpn/tls_cryp
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Yeah, I forgot to apply and commit -- sorry.
I guess I'll send again if this is an acceptable patch and my MTA didn't screw
it up ?
Please let me know .. thanks
‐‐‐ Original Message ‐‐‐
On Wednesday, 28 April 2021 18:44, tincantech wrot
‐‐‐ Original Message ‐‐‐
On Wednesday, 28 April 2021 18:48, tincantech via Openvpn-devel
wrote:
> Yeah, I forgot to apply and commit -- sorry.
>
> I guess I'll send again if this is an acceptable patch and my MTA didn't
> screw it up ?
> Please let me know .. th
would be willing to accept my proposed patch and
> then I will persist to find a way.
>
> If you will not accept the addition then please let me know.
>
> Thanks
> R
>
> ‐‐‐ Original Message ‐‐‐
> On Wednesday, 28 April 2021 18:48, tincantech via Openvpn-devel
&
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Under Windows, programmatically retrieving the parent process ID of
the openvpn instance which called a script is practically impossible.
The only sensible way, currently available, is to write a PID file.
This patch adds a single integer variable,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
‐‐‐ Original Message ‐‐‐
On Thursday, 29 April 2021 18:15, Richard T Bonhomme
wrote:
> From: string vest stringves...@gmail.com
>
> Under Windows, programmatically retrieving the parent process ID of
> the openvpn instance which called a s
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi,
‐‐‐ Original Message ‐‐‐
On Tuesday, 4 May 2021 11:50, Arne Schwabe wrote:
> Am 29.04.21 um 19:15 schrieb Richard T Bonhomme:
>
> > From: string vest stringves...@gmail.com
> > Under Windows, programmatically retrieving the parent proc
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi,
‐‐‐ Original Message ‐‐‐
On Tuesday, 4 May 2021 13:43, tincantech via Openvpn-devel
wrote:
> Hi,
>
> ‐‐‐ Original Message ‐‐‐
> On Tuesday, 4 May 2021 11:50, Arne Schwabe a...@rfc2549.org wrote:
>
> >
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi,
‐‐‐ Original Message ‐‐‐
On Tuesday, 4 May 2021 20:41, Selva Nair wrote:
> On Tue, May 4, 2021 at 3:04 PM tincantech via Openvpn-devel
> openvpn-devel@lists.sourceforge.net wrote:
>
> > Due to the inordinate resist
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Sent with ProtonMail Secure Email.
‐‐‐ Original Message ‐‐‐
On Tuesday, 4 May 2021 21:36, tincantech via Openvpn-devel
wrote:
> Hi,
>
> ‐‐‐ Original Message ‐‐‐
> On Tuesday, 4 May 2021 20:41, Selva Nair selva.n.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi,
‐‐‐ Original Message ‐‐‐
On Wednesday, 5 May 2021 08:51, Arne Schwabe wrote:
> > > Could you explain why you need the process ID of the daemon? I am trying
> > > to figure out why that is needed. I also don't understand the secure in
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi,
‐‐‐ Original Message ‐‐‐
On Monday, 10 May 2021 18:29, Gert Doering wrote:
> Hi,
>
> On Wed, May 05, 2021 at 10:00:37PM +, tincantech via Openvpn-devel wrote:
>
> > thanks for the feedback, I can resubmit with
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi,
> 4. Having my user account recently locked out of Trac.
>
> I expect that I can even ''predict'' what that is with regard to.
>
> ...
>
Seems I typed my ludicrously long password incorrectly..
The rest still stands.
Sorry for the n
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi,
‐‐‐ Original Message ‐‐‐
On Monday, 10 May 2021 23:10, Selva Nair wrote:
> On Mon, May 10, 2021 at 4:24 PM tincantech via Openvpn-devel
> openvpn-devel@lists.sourceforge.net wrote:
>
> > -BEGIN PGP SIGNED MESSAG
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Sent with ProtonMail Secure Email.
‐‐‐ Original Message ‐‐‐
On Tuesday, 11 May 2021 07:02, Gert Doering wrote:
> Hi,
>
> On Mon, May 10, 2021 at 06:10:33PM -0400, Selva Nair wrote:
>
> > > > So, there is an ACK-and-merge pending :-)
>
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi,
I was in the process of reviewing this patch when I found that protonmail
had changed most of the git '+' to '-', see below.
I have reported a bug to protonmail.
Anyway, I can see a few typos and some other odd errors.
Hopefully, protonmail wi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi,
I used sed to create my own reply ..
comments inline.
‐‐‐ Original Message ‐‐‐
On Wednesday, 12 May 2021 14:15, Arne Schwabe wrote:
> This is meant to give new users a quickstart for a useable OpenVPN
> setup. Our own documentation
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi,
missed one..
‐‐‐ Original Message ‐‐‐
On Thursday, 13 May 2021 22:48, tincantech via Openvpn-devel
wrote:
> Hi,
>
> I used sed to create my own reply ..
>
> comments inline.
>
> ‐‐‐ Original Message ‐
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi,
I think it would useful to allow comment inside the markers.
EG:
# alice
67:1F:A5:CA:26:98:BA:40:D9:EB:6A:5B:C1:64:8C:8E:66:6E:7A:22:26:73:96:6A:5E:9B:B3:17:8F:F8:C6:9C
# bob
55:B6:3F:AD:BC:A0:8C:EF:00:B3:2F:A5:46:46:83:82:6F:34:86:8D:23:2B:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi,
‐‐‐ Original Message ‐‐‐
On Monday, 17 May 2021 16:31, Gert Doering wrote:
> Hi,
>
> On Mon, May 17, 2021 at 02:57:32PM +, tincantech via Openvpn-devel wrote:
>
> > I think it would useful to allow comment inside
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi,
‐‐‐ Original Message ‐‐‐
On Wednesday, 12 May 2021 14:15, Arne Schwabe wrote:
> This is meant to give new users a quickstart for a useable OpenVPN
> setup. Our own documentation is lacking in this regard and many often
> tutorials that
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi,
‐‐‐ Original Message ‐‐‐
On Monday, 17 May 2021 18:16, tincantech via Openvpn-devel
wrote:
> Hi,
>
> ‐‐‐ Original Message ‐‐‐
> On Wednesday, 12 May 2021 14:15, Arne Schwabe a...@rfc2549.org wrote:
>
> >
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi,
‐‐‐ Original Message ‐‐‐
On Tuesday, 18 May 2021 13:21, Arne Schwabe wrote:
> Am 17.05.21 um 19:16 schrieb tincantech:
>
> > Hi,
> > ‐‐‐ Original Message ‐‐‐
> > On Wednesday, 12 May 2021 14:15, Arne Schwabe a...@rfc2549.org wr
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi,
‐‐‐ Original Message ‐‐‐
On Monday, 17 May 2021 20:07, tincantech wrote:
> Hi,
>
> ‐‐‐ Original Message ‐‐‐
> On Monday, 17 May 2021 18:16, tincantech via Openvpn-devel
> openvpn-devel@lists.sourceforge.net
-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
-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
-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-
-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
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi,
again, I do not understand why openvpn choose to switch to .pem
for this tutorial. PEM -> Private Email, which this is not.
You have a certificate and a key and every other openvpn tutorial
on openvpn and probably the entire planet uses .crt an
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi,
‐‐‐ Original Message ‐‐‐
On Thursday, 20 May 2021 19:30, Arne Schwabe wrote:
> Am 20.05.2021 um 18:56 schrieb tincantech:
>
> > Hi,
> > again, I do not understand why openvpn choose to switch to .pem
> > for this tutorial. PEM -> Priv
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Sent with ProtonMail Secure Email.
‐‐‐ Original Message ‐‐‐
On Thursday, 20 May 2021 22:05, Jan Just Keijser wrote:
> Hi,
>
> On 20/05/21 21:49, tincantech via Openvpn-devel wrote:
>
> > > > Hi,
> > >
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi,
‐‐‐ Original Message ‐‐‐
On Thursday, 20 May 2021 22:22, Jan Just Keijser wrote:
> On 20/05/21 23:12, tincantech wrote:
>
> > [...]
> >
> > > > So, why switch to .pem when it has never been used before by openvpn?
> > > > If you are al
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi,
-‐‐ Original Message ‐‐‐
On Thursday, 20 May 2021 22:35, tincantech via Openvpn-devel
wrote:
> Hi,
>
> ‐‐‐ Original Message ‐‐‐
> On Thursday, 20 May 2021 22:22, Jan Just Keijser janj...@nikhef.nl wrote:
>
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi,
‐‐‐ Original Message ‐‐‐
On Friday, 21 May 2021 00:40, tincantech wrote:
> I would like to hammer one final nail into this discussion.
>
> Openvpn option names and inline tags ALL use ificate .crt and
> .key.
>
> They do not use .pe
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi,
Is this expected ?
Server log:
2021-05-24 14:58:03 us=534606 10.10.201.226:60276 TLS CRYPT V2 VERIFY SCRIPT OK
2021-05-24 14:58:03 us=558066 10.10.201.226:60276 VERIFY KU OK
2021-05-24 14:58:03 us=558105 10.10.201.226:60276 Validating certific
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi,
‐‐‐ Original Message ‐‐‐
On Monday, 24 May 2021 18:39, Selva Nair wrote:
> Hi,
>
> On Mon, May 24, 2021 at 10:09 AM tincantech via Openvpn-devel
> openvpn-devel@lists.sourceforge.net wrote:
>
> > -BEG
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi,
I may be wrong but this is the order as it appears to me:
‐‐‐ Original Message ‐‐‐
On Monday, 24 May 2021 18:39, Selva Nair wrote:
> > Server log:
> > 2021-05-24 14:58:03 us=534606 10.10.201.226:60276 TLS CRYPT V2 VERIFY
> > SCRIPT
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi,
‐‐‐ Original Message ‐‐‐
On Monday, 24 May 2021 21:43, Arne Schwabe wrote:
> Am 24.05.2021 um 16:07 schrieb tincantech via Openvpn-devel:
>
> > Hi,
> > Is this expected ?
>
> I might to check if it is even
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Him
I read through it and it looks good to me.
One tiny omission inserted: Scroll to end.
Regards
R
Sent with ProtonMail Secure Email. Which still can't handle patches.
‐‐‐ Original Message ‐‐‐
On Wednesday, 2 June 2021 04:42, wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi
text corrections.
Sorry about protonmail making '+' to '-'
‐‐‐ Original Message ‐‐‐
On Wednesday, May 12th, 2021 at 14:15, Arne Schwabe wrote:
> Signed-off-by: Arne Schwabe a...@rfc2549.org
>
> doc/man-sections/protocol-options.rst
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Ignore me .. this has been applied
Sent with ProtonMail Secure Email.
‐‐‐ Original Message ‐‐‐
On Sunday, June 20th, 2021 at 19:09, tincantech via Openvpn-devel
wrote:
> Hi
>
> text corrections.
>
> Sorry about protonmai
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi,
the openvpn-server systemd unit file currently make use of PrivateTmp=True,
this denies the openvpn process access to /tmp (and /var/tmp).
This setting also does not provide the systemd assigned location for temporary
files to the openvpn proce
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi
the problem is three fold:
3.
How would I then point scripts to the systemd assigned folder ?
(Yet another env var: systemd_private_tmp)
The most logical answer is "To take matters into my own hands"
and specify my own temporary location but tha
ech via Openvpn-devel wrote:
>
> > Hi
>
> [... copied from first mail ...]
>
> > > Thus the problem is two fold:
> >
> > It is not possible to pre-determine a temporary directory within the systemd
> >
> > PrivateTmp assigned folder within an open
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi,
this is a comment about a comment which this patch is not changing
but the comment is so awful I thought it best to make a note.
See below.
Also, two typos. And FYI, 'anymore' ought to be 'any more'
R
Sent with ProtonMail Secure Email, which
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi,
six minor improvements, could probably be made on commit.
One comment: This tutorial will not work on Windows because it relies
on a bashism to generate the self-signed certs. There is no mention
of that anywhere, may be it could be pointed ou
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi,
Sent with ProtonMail Secure Email.
‐‐‐ Original Message ‐‐‐
On Monday, August 2nd, 2021 at 10:52, Arne Schwabe wrote:
> Signed-off-by: Arne Schwabe a...@rfc2549.org
>
> Patch v3: Some minor cleanups in the script (rename CNs, add mor
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi,
12 minor corrections
Sent with ProtonMail Secure Email.
‐‐‐ Original Message ‐‐‐
On Monday, August 2nd, 2021 at 12:46, Arne Schwabe wrote:
> TLS 1.0 should be allowed anymore in a sensible default configuration. Bump
> the default t
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi,
V2 - 13 minor correction ;-)
‐‐‐ Original Message ‐‐‐
On Monday, August 2nd, 2021 at 12:55, Arne Schwabe wrote:
> TLS 1.0 should be allowed anymore in a sensible default configuration. Bump
TLS 1.0 should *not* be allowed
> the d
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi,
a few more wrinkles to smooth out.
Sent with ProtonMail Secure Email.
‐‐‐ Original Message ‐‐‐
On Wednesday, August 11th, 2021 at 08:29, Antonio Quartulli
wrote:
> Hi,
>
> On 05/08/2021 20:09, Arne Schwabe wrote:
> > TLS 1.0 shoul
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Sent with ProtonMail Secure Email.
‐‐‐ Original Message ‐‐‐
On Monday, September 6th, 2021 at 14:19, Arne Schwabe wrote:
> Am 04.09.21 um 11:56 schrieb Antonio Quartulli:
>
> > The new condition is equivalent to the old one, but easier
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
The commit message is incorrect.
Not *always* but "after a renegotiation" then *always*
I'll resubmit again after some final testing.
R
Sent with ProtonMail Secure Email.
‐‐‐ Original Message ‐‐‐
On Thursday, September 16th, 2021 at 17:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi,
I NAK this for the following reasons.
The original problem:
"Openvpn does not set common_name for --client-disconnect",
for reasons which have not been identified, no longer occurs.
The code has changed enough since 2011 that a new problem
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi
Sent with ProtonMail Secure Email.
‐‐‐ Original Message ‐‐‐
On Monday, November 8th, 2021 at 12:23, Frank Lichtenheld
wrote:
> > Arne Schwabe a...@rfc2549.org hat am 08.11.2021 12:36 geschrieben:
> >
> > Am 07.11.21 um 18:40 schrieb
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
One tiny typo:
Sent with ProtonMail Secure Email.
‐‐‐ Original Message ‐‐‐
On Thursday, November 11th, 2021 at 13:00, Arne Schwabe
wrote:
> This allows OpenVPN to load non-default providers. This is mainly
>
> useful for loading the leg
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi
Sent with ProtonMail Secure Email.
‐‐‐ Original Message ‐‐‐
user/pass.
On Monday, November 15th, 2021 at 13:11, Ruben Herold
wrote:
> On Mon, Nov 15, 2021 at 02:45:53PM +0200, Lev Stipakov wrote:
>
> > Are you sure your problem cannot
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Superseded - Due to incorrect option name.
Sent with ProtonMail Secure Email.
‐‐‐ Original Message ‐‐‐
On Tuesday, November 16th, 2021 at 14:49, Richard T Bonhomme
wrote:
> Signed-off-by: Richard T Bonhomme tincant...@protonmail.com
>
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Seems I jumped the gun a little..
NACK, --compress is not deprecated in 2.4
Sorry
R
Sent with ProtonMail Secure Email.
‐‐‐ Original Message ‐‐‐
On Friday, November 26th, 2021 at 14:48, Antonio Quartulli
wrote:
> Hi,
>
> On 26/11/2021
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
It seems only fair to warn the OpenVPN community that Version 2.5.5 has had
bugs identified.
A new release v2.5.6 is planned for the coming week, or so..
Regards
Richard
Sent with ProtonMail Secure Email.
‐‐‐ Original Message ‐‐‐
On Wedn
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Seems I was too hasty here. OpenVPN 2.5.5 is the current release
and there are no bugs severe enough to warrant a version 2.5.6, at this time.
Sorry for the confusion.
Regards
Richard
Sent with ProtonMail Secure Email.
‐‐‐ Original Message
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
May as well attribute this correctly.
* tincant...@protonmail.com
Protonmail, now so badly mangles mail on reply that I may have to go back to
gmail.
-BEGIN PGP SIGNATURE-
Version: ProtonMail
wsBzBAEBCAAGBQJiC7VvACEJEE+XnPZrkLidFiEECbw9RG
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
EasyRSA development is back on-track.
Happy to help.
BR
--- Original Message ---
On Monday, March 28th, 2022 at 14:56, Michael Baentsch wrote:
> Am 28.03.22 um 13:52 schrieb Arne Schwabe:
> >
> > Easyrsa has become also separate projec
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi nsh...@gmail.com
It is common procedure to keep security concerns to the security@ mailing list.
To have your concerns expertly reviewed, it is advisable to follow standard
security and disclosure procedures.
While this thread is, no doubt, amu
80 matches
Mail list logo
