大网数据广告活动
服务器运维问答

Nginx with 384-Bit ECC certificate and OpenSSL but why is curve secp256r1 not usable?

· 52CE 我爱测

Im using Nginx 1.11.7 with OpenSSL 1.1.0c on Debian 8 and have a self-signed ECC certificate with 384 Bit Key for testing purposes. I would like to use the curves X25519 , secp384r1 and secp256r1 . Nginx starts normally with X255…

问题原文

原帖链接 · Henrik N. · CC BY-SA 4.0

Im using Nginx 1.11.7 with OpenSSL 1.1.0c on Debian 8 and have a self-signed ECC certificate with 384 Bit Key for testing purposes.

I would like to use the curves X25519, secp384r1 and secp256r1.

Nginx starts normally with X25519 and secp384r1 enabled in Nginx config:

ssl_ecdh_curve X25519:secp384r1;

But refuses to restart/reload when using secp256r1:

ssl_ecdh_curve secp256r1;

The error message:

SSL_CTX_set1_curves_list("secp256r1") failed (SSL:)

So how can I use the secp256r1 curve with the setup mentioned above?

已采纳解答

原帖链接 · Henrik N. · CC BY-SA 3.0

Turns out P-256 has been removed from the list.

See:

Why Is TLS 1.3 an advancement over TLS 1.2 or 1.1?
TLS 1.3 removes support for known insecure ciphers such as RC4, DES, 3DES and export grade ciphers as well older hashing algorithms e.g. SHA-1 and MD5. These are welcome changes that should help to reduce the possibility of further vulnerabilities such as SWEET32 and FREAK being present within the code of TLS libraries e.g. OpenSSL.

This reduces the attack surface (defined within the second paragraph of this blog post) of TLS 1.3 but the improvements don’t stop there. Cipher suites such as NIST P-256 and AES-GCM are being removed as primitives with only x25519, ChaCha20 and Poly1305 remaining developed by Dan Bernstein (who uses the handle djb).

From here: securityinaction.wordpress.com

摘自公开归档,保留原文语言,版式经整理,外部媒体与邮箱地址已移除。

资料来源与适用范围

资料来源
Server Fault
适用范围
以原帖系统、软件版本与发布日期为准(2016-12-27)
内容语言
中文;命令、路径和错误标识保留技术原文
本地收录日期
2026-11-15
授权说明
CC BY-SA 4.0 / CC BY-SA 3.0

正文与所需资源由本站本地存储。查看来源及更新记录 ↗

请按适用版本和实际日志确认原因;本站没有对每一种系统或设备逐项执行文中的操作。