Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

#

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Jump to bottom

Reference RFC7919 for choosing DHE Group Param #2

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Reference RFC7919 for choosing DHE Group Param #2

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
16 changes: 12 additions & 4 deletions docs/SSL_TLS_Deployment_Best_Practices.xml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -341,10 +341,18 @@ EDH-RSA-DES-CBC3-SHA</programlisting></para>
</footnote> The researchers discovered that lower-strength DH key exchanges (e.g.,
768 bits) can easily be broken and that some well-known 1,024-bit DH groups can be
broken by state agencies. To be on the safe side, if deploying DHE, configure it
with at least 2,048 bits of security. Some older clients (e.g., Java 6) might not
support this level of strength. For performance reasons, most servers should prefer
ECDHE, which is both stronger and faster. The <literal>secp256r1</literal> named
curve (also known as <literal>P-256</literal>) is a good choice in this case.</para>
with at least 2,048 bits of security. Ideally, using one of the DH groups specified
in <literal>RFC7919</literal>: Negotiated Finite Field Diffie-Hellman Ephemeral Parameters for
Transport Layer Security (TLS)
<footnote>
<para><link xlink:href="https://tools.ietf.org/html/rfc7919">RFC7919: Negotiated
Finite Field Diffie-Hellman Ephemeral Parameters for Transport Layer
Security (TLS)</link> (retrieved 9 June 2020)</para>
</footnote>
Some older clients (e.g., Java 6) might not support this level of strength. For
performance reasons, most servers should prefer ECDHE, which is both stronger and
faster. The <literal>secp256r1</literal> named curve (also known as <literal>P-256</literal>)
is a good choice in this case.</para>
</section>
<section renderas="sect3">
<title>2.7 Mitigate Known Problems</title>
Expand Down