public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Adolf Belka <adolf.belka@ipfire.org>
To: development@lists.ipfire.org
Subject: [PATCH 1/2] openssl: Fix for Bug#13117 - adds legacy option in for openssl extraction of cert & key
Date: Sun, 21 May 2023 14:45:43 +0200	[thread overview]
Message-ID: <20230521124544.3457345-1-adolf.belka@ipfire.org> (raw)

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

- OpenSSL-3.x gives an error when trying to open insecure .p12 files to extract the cert
   and key for the insecure package download option.
- To make this work the -legacy option is needed in the openssl command, which requires
   the legacy.so library to be available.
- Successfully tested on a vm system.
- Patch set built on Master (CU175 Testing)

Tested-by: Adolf Belka <adolf.belka(a)ipfire.org>
Signed-off-by: Adolf Belka <adolf.belka(a)ipfire.org>
---
 config/rootfiles/common/openssl | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/config/rootfiles/common/openssl b/config/rootfiles/common/openssl
index e29bc6dc1..44ae2cda9 100644
--- a/config/rootfiles/common/openssl
+++ b/config/rootfiles/common/openssl
@@ -160,7 +160,7 @@ usr/lib/libcrypto.so.3
 usr/lib/libssl.so
 usr/lib/libssl.so.3
 #usr/lib/ossl-modules
-#usr/lib/ossl-modules/legacy.so
+usr/lib/ossl-modules/legacy.so
 #usr/lib/pkgconfig/libcrypto.pc
 #usr/lib/pkgconfig/libssl.pc
 #usr/lib/pkgconfig/openssl.pc
-- 
2.40.1


             reply	other threads:[~2023-05-21 12:45 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-21 12:45 Adolf Belka [this message]
2023-05-21 12:45 ` [PATCH 2/2] ovpnmain.cgi: Fixes Bug#13117 - adds legacy option to openssl commands for cert & key extraction Adolf Belka

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=20230521124544.3457345-1-adolf.belka@ipfire.org \
    --to=adolf.belka@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