From: ummeegge <ummeegge@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH 1/3] OpenVPN: Introduce advanced encryption section
Date: Tue, 08 Dec 2020 18:28:21 +0100 [thread overview]
Message-ID: <b302d7923a5c9fc063e24e431a3ae1138851bd2d.camel@ipfire.org> (raw)
In-Reply-To: <20201203120807.20694-1-erik.kapfer@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 601 bytes --]
Hi all,
there are meanwhile some enhancements and one fix.
- The are translations (human) in four languages available -->
https://community.ipfire.org/t/please-for-help-to-translate-some-strings/3942
Russian, Polish and Turkish are also there but machine translated.
- There is a check for weak algorithms, also for the HMAC SHA1 with the
warning to change this settings as soon as possible since they are
deprecated.
- A fix is included since tls-crypt wasn´t parsed into client.ovpn in
'insecure' mode.
I would send a version 2 with all changes but now may split into 4-5
patches ?
Best,
Erik
next prev parent reply other threads:[~2020-12-08 17:28 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-03 12:08 ummeegge
2020-12-03 12:08 ` [PATCH 2/3] OpenVPN: Control-Channel encryption settings ummeegge
2020-12-03 12:08 ` [PATCH 3/3] OpenVPN: Integrate TLS-Authentication and HMAC selection ummeegge
2020-12-08 17:28 ` ummeegge [this message]
2020-12-29 10:29 ` [PATCH 1/3] OpenVPN: Introduce advanced encryption section Michael Tremer
2020-12-10 16:59 ` [PATCH v2 1/7] " ummeegge
2020-12-10 16:59 ` [PATCH v2 2/7] OpenVPN: Substitute --cipher with --data-cipher-fallback ummeegge
2020-12-10 16:59 ` [PATCH v2 3/7] OpenVPN: Warning for broken algorithms ummeegge
2020-12-10 16:59 ` [PATCH v2 4/7] OpenVPN: New ciphers and HMACs for N2N ummeegge
2020-12-10 16:59 ` [PATCH v2 5/7] OpenVPN: Control-Channel encryption settings ummeegge
2020-12-10 16:59 ` [PATCH v2 6/7] OpenVPN: Moved HMAC to advanced crypto section ummeegge
2020-12-10 16:59 ` [PATCH v2 7/7] OpenVPN: Moved TLS auth to advanced encryption section ummeegge
2020-12-14 13:03 ` ummeegge
2020-12-14 13:43 ` Michael Tremer
2020-12-14 15:12 ` ummeegge
2020-12-15 11:58 ` Michael Tremer
2020-12-14 13:44 ` Paul Simmons
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=b302d7923a5c9fc063e24e431a3ae1138851bd2d.camel@ipfire.org \
--to=ummeegge@ipfire.org \
--cc=development@lists.ipfire.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox