From: Paul Simmons <redneckmother@hughes.net>
To: development@lists.ipfire.org
Subject: Re: AW: [PATCH] change Apache TLS cipher list to "Mozilla Modern"
Date: Sat, 11 Nov 2017 08:48:36 -0600 [thread overview]
Message-ID: <1510411716.21859.6.camel@hughes.net> (raw)
In-Reply-To: <1510269464.2945.18.camel@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 397 bytes --]
+1 Security
Thank you,
Paul
On Thu, 2017-11-09 at 23:17 +0000, Michael Tremer wrote:
> Hi,
>
> so how do we handle this?
>
> We now have the argument for better security against the argument for
> better compatibility.
>
> Indeed this is not an easy question. So please everybody else who has
> an opinion on this step forward and then I will just count the votes.
>
> Best,
> -Michael
>
next prev parent reply other threads:[~2017-11-11 14:48 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-08 21:17 Wolfgang Apolinarski
2017-11-08 21:44 ` Peter Müller
2017-11-09 21:35 ` AW: " Wolfgang Apolinarski
2017-11-09 23:17 ` Michael Tremer
2017-11-10 11:53 ` Horace Michael
2017-11-11 14:48 ` Paul Simmons [this message]
2017-11-11 19:27 ` Peter Müller
2017-11-11 19:48 ` Tom Rymes
2017-11-14 15:28 ` Michael Tremer
2017-11-14 23:53 ` AW: " Wolfgang Apolinarski
2017-11-20 19:12 ` Peter Müller
2017-11-11 19:38 ` AW: " Matthias Fischer
2017-11-11 19:39 ` Peter Müller
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=1510411716.21859.6.camel@hughes.net \
--to=redneckmother@hughes.net \
--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