public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: "Peter Müller" <peter.mueller@link38.eu>
To: development@lists.ipfire.org
Subject: [PATCH] delete obsolete patch for OpenSSL 1.0.x
Date: Sat, 24 Mar 2018 15:59:59 +0100	[thread overview]
Message-ID: <20180324155959.3813fdb9.peter.mueller@link38.eu> (raw)

[-- Attachment #1: Type: text/plain, Size: 1327 bytes --]

This patch became obsolete since we use OpenSSL 1.1.x in Core Update
120 and onward, where a similar patch already exists.

Signed-off-by: Peter Müller <peter.mueller(a)link38.eu>
---
 src/patches/openssl-1.0.2h-weak-ciphers.patch | 12 ------------
 1 file changed, 12 deletions(-)
 delete mode 100644 src/patches/openssl-1.0.2h-weak-ciphers.patch

diff --git a/src/patches/openssl-1.0.2h-weak-ciphers.patch b/src/patches/openssl-1.0.2h-weak-ciphers.patch
deleted file mode 100644
index d1ec6a2af..000000000
--- a/src/patches/openssl-1.0.2h-weak-ciphers.patch
+++ /dev/null
@@ -1,12 +0,0 @@
-diff -Naur openssl-1.0.2h.org/ssl/ssl.h openssl-1.0.2h/ssl/ssl.h
---- openssl-1.0.2h.org/ssl/ssl.h	2016-05-03 15:44:42.000000000 +0200
-+++ openssl-1.0.2h/ssl/ssl.h	2016-05-03 18:49:10.393302264 +0200
-@@ -338,7 +338,7 @@
-  * The following cipher list is used by default. It also is substituted when
-  * an application-defined cipher list string starts with 'DEFAULT'.
-  */
--# define SSL_DEFAULT_CIPHER_LIST "ALL:!EXPORT:!LOW:!aNULL:!eNULL:!SSLv2"
-+# define SSL_DEFAULT_CIPHER_LIST "ALL:!EXPORT:!LOW:!aNULL:!eNULL:!SSLv2:!RC2:!DES"
- /*
-  * As of OpenSSL 1.0.0, ssl_create_cipher_list() in ssl/ssl_ciph.c always
-  * starts with a reasonable order, and all we have to do for DEFAULT is
-- 
2.13.6


             reply	other threads:[~2018-03-24 14:59 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-24 14:59 Peter Müller [this message]
2018-03-26 13:35 ` Michael Tremer
2018-03-26 18:47   ` 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=20180324155959.3813fdb9.peter.mueller@link38.eu \
    --to=peter.mueller@link38.eu \
    --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