public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH v2 7/7] OpenVPN: Moved TLS auth to advanced encryption section
Date: Mon, 14 Dec 2020 14:43:02 +0100	[thread overview]
Message-ID: <31FB570C-471A-4740-84F4-93FF8CD143D7@ipfire.org> (raw)
In-Reply-To: <f42d0d90061b13c1229c65d4887c97d682650235.camel@ipfire.org>

[-- Attachment #1: Type: text/plain, Size: 1403 bytes --]

Hello Erik,

Yes, I am very much interested in this.

And I have spent pretty much an hour to make sense out of all of this, and unfortunately have to report that I failed.

I have the problem that I cannot get on top of these things. You are submitting *massive* patchsets, in this case I even believe that the whole things has been submitted a second time, although I do not know if there are any changes.

I could not even find out *what* you are actually trying to do. There are more and more buttons being added and I have not the slightest idea what I am supposed to do with them. I have given my thoughts about the cipher selection and I felt that I have not been heard.

I fear that this is all way too complicated. I cannot review what I do not even understand what the desired outcome is. And failing to understand that either means that it is either way too complicated or I have not read enough anywhere about all of this.

So, could you please summarise for me what you want to achieve here?

Is this supposed to make OpenVPN more compatible, secure, or anything else?

Why do we not talk about this before things are being implemented, or did I just miss the discussion?

-Michael

> On 14 Dec 2020, at 14:03, ummeegge <ummeegge(a)ipfire.org> wrote:
> 
> Hi all,
> just wanted to ask if there is still interest in this patch series ?
> 
> Best,
> 
> Erik
> 


  reply	other threads:[~2020-12-14 13:43 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-03 12:08 [PATCH 1/3] OpenVPN: Introduce " 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 ` [PATCH 1/3] OpenVPN: Introduce advanced encryption section ummeegge
2020-12-29 10:29   ` 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 [this message]
2020-12-14 15:12         ` ummeegge
2020-12-15 11:58           ` Michael Tremer
2020-12-14 13:44       ` Paul Simmons
     [not found] <949358d1ea0424fe6b1f4c78c24b37c5e79ef0ef.camel@ipfire.org>
2020-12-29 10:44 ` Michael Tremer
2021-01-13  9:18   ` ummeegge
2021-01-14 18:50     ` Adolf Belka
2021-01-15  4:56       ` ummeegge
2021-01-22 22:08         ` Adolf Belka
2021-01-23  7:28           ` ummeegge
2021-03-09 14:55         ` Adolf Belka (ipfire)

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=31FB570C-471A-4740-84F4-93FF8CD143D7@ipfire.org \
    --to=michael.tremer@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