From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Updated Apache configuration
Date: Sat, 28 Oct 2017 13:45:39 +0100 [thread overview]
Message-ID: <1509194739.2749.17.camel@ipfire.org> (raw)
In-Reply-To: <004b01d34e89$160a82b0$421f8810$@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 1337 bytes --]
Hi,
On Thu, 2017-10-26 at 20:34 +0200, Wolfgang Apolinarski wrote:
> Hi!
>
> This last patch is just a suggestion on how an apache configuration based on the Mozilla suggestion would look like.
This seems to differ a little bit from what I have seen on here:
https://mozilla.github.io/server-side-tls/ssl-config-generator/
Where did you get this from?
> It includes a 4096-bit DH parameter that is used instead of the one defined in RFC 5144.
So since they are only suggesting cipher suites that either use ECDHE
or no PFS at all there is no need for generating the DH parameter
offline. Is that an option that could also work for us?
I do not care to be compatible with Windows XP. If that is the only
system from which it is possible to configure your firewall you are
doing it wrong.
> Generating the DH parameter has been the suggested approach by the weakdh-team. Of course, as already discussed, this would be the standard parameter for IPFire, then, similar as the already chosen EC curve and similar to the standard parameters defined in RFC 5144.
Best,
-Michael
P.S. You can send these comments as a cover letter or even put them
directly into the commit message. I didn't see the connection in the
first place between this email and the patch.
>
> Best regards,
> Wolfgang
>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2017-10-28 12:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-26 18:34 Wolfgang Apolinarski
2017-10-28 12:45 ` Michael Tremer [this message]
2017-10-28 12:48 ` Michael Tremer
2017-11-07 19:03 ` 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=1509194739.2749.17.camel@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