public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: "Peter Müller" <peter.mueller@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH] OpenVPN: mark CBC ciphers as weak in WebUI
Date: Mon, 10 Jun 2019 19:08:00 +0000	[thread overview]
Message-ID: <8edaf74e-2912-1d32-9c23-234e1eadf1d2@ipfire.org> (raw)
In-Reply-To: <4FDE0AC7-76CB-4B9A-A5D3-E77EE9DFED5C@ipfire.org>

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

Hello Michael,

thanks for your comments.

> Hi,
> 
> I think I can ACK this although we definitely should change the default. I have raised that a couple of times before.
Yes. This is true for IPsec as well... Patch is in my pipeline...
> 
> I also do not like having a very long list of ciphers that are weak. There are not too many left which are “strong”. But yeah, what can you do?
As far as I am concerned, there is little "strong" cryptography left indeed.
It's basically only TLS >= 1.2 with AEAD (e.g. GCM) ciphers and Forward Secrecy.

Speaking about RFC 8446, this is more or less what survived discussions before
standardizing TLS 1.3 ... :-)
> 
> I will wait for Erik to ack this, too.
> 
> -Michael
Thanks, and best regards,
Peter Müller
-- 
The road to Hades is easy to travel.
	-- Bion of Borysthenes

  reply	other threads:[~2019-06-10 19:08 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-10 18:36 Peter Müller
2019-06-10 18:47 ` Michael Tremer
2019-06-10 19:08   ` Peter Müller [this message]
2019-06-10 19:12     ` Michael Tremer
2019-06-10 19:49       ` ummeegge
2019-06-11 10:17         ` Michael Tremer

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=8edaf74e-2912-1d32-9c23-234e1eadf1d2@ipfire.org \
    --to=peter.mueller@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