From: coroner@...2290... Date: Mon, 4 Sep 2017 10:10:12 +0200 Message-Id: <20170904081012.1975-1-coroner@...2290...> In-Reply-To: <01ea7971-ae7a-573b-8845-30b04b0b8112@...1856...> References: <01ea7971-ae7a-573b-8845-30b04b0b8112@...1856...> MIME-Version: 1.0 Subject: [Openvpn-devel] [PATCH] OpenSSL: Always set SSL_OP_CIPHER_SERVER_PREFERENCE flag List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable To: openvpn-devel@lists.sourceforge.net From: Szil=C3=A1rd Pfeiffer * safe bet to say that server admins are better at updating their configs than client users are and if client do want to restrict their ciphers, they should simply evict the ciphers they don't want from their cipher suite * mbed TLS and OpenSSL behave more similar with the SSL_OP_CIPHER_SERVER_PREFERENCE flag --- src/openvpn/ssl_openssl.c | 3 +++ 1 file changed, 3 insertions(+) diff --git a/src/openvpn/ssl_openssl.c b/src/openvpn/ssl_openssl.c index 597c62d8..92a662b5 100644 --- a/src/openvpn/ssl_openssl.c +++ b/src/openvpn/ssl_openssl.c @@ -252,6 +252,9 @@ tls_ctx_set_options(struct tls_root_ctx *ctx, unsigned = int ssl_flags) { sslopt |=3D SSL_OP_NO_TLSv1_2; } +#endif +#ifdef SSL_OP_CIPHER_SERVER_PREFERENCE + sslopt |=3D SSL_OP_CIPHER_SERVER_PREFERENCE; #endif sslopt |=3D SSL_OP_NO_COMPRESSION; SSL_CTX_set_options(ctx->ctx, sslopt); --=20 2.14.1