linux-mtd.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: David Oberhollenzer <david.oberhollenzer@sigma-star.at>
To: Bastian Germann <bage@linutronix.de>,
	Richard Weinberger <richard.weinberger@gmail.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: [PATCH] mkfs.ubifs: remove OPENSSL_no_config()
Date: Fri, 25 Sep 2020 05:15:24 +0200	[thread overview]
Message-ID: <1bb381ec-1f5f-3844-d904-7dd2af58577d@sigma-star.at> (raw)
In-Reply-To: <64f36cbd-9ab5-1b37-c4b3-c33b5daf6df8@linutronix.de>

On 9/24/20 6:40 PM, Bastian Germann wrote:
> Am 25.07.20 um 10:24 schrieb Richard Weinberger:
>> On Fri, Jul 24, 2020 at 10:00 AM <bage@linutronix.de> wrote:
>>>
>>> From: Torben Hohn <torben.hohn@linutronix.de>
>>>
>>> Especially for the pkcs11 engine, a configuration is required
>>> because the provider has to be configured.
>>>
>>> Its not clear why OPENSSL_no_config() is called.
>>
>> My best guess is because on old openssl versions it used to work.
>>
>>> Remove OPENSSL_no_config() and call OPENSSL_config(NULL)
>>> instead.
>>
>> David, can you please check whether this change works with all openssl versions
>> we want to support?
>>
> 
> Are there any news on this?
> 

Sorry for the delay. I did some research on this in August but being busy at
the time eventually forgot about the thread.

The latest changes that I found in the change log dated back to OpenSSL 0.9.7.
Walking through the git log for the implementation seems to confirm that.

However, recent man pages say, that the OPENSSL_config functions are deprecated
since OpenSSL 1.1.0 and OPENSSL_init_crypto should be used now, so the patch
might require an extra #if for newer OpenSSL versions.

______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/

  reply	other threads:[~2020-09-25  3:16 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-24  7:47 [PATCH] mkfs.ubifs: remove OPENSSL_no_config() bage
2020-07-25  8:24 ` Richard Weinberger
2020-09-24 16:40   ` Bastian Germann
2020-09-25  3:15     ` David Oberhollenzer [this message]
2020-09-29 14:05       ` Bastian Germann
2020-10-18 20:44         ` David Oberhollenzer

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=1bb381ec-1f5f-3844-d904-7dd2af58577d@sigma-star.at \
    --to=david.oberhollenzer@sigma-star.at \
    --cc=bage@linutronix.de \
    --cc=linux-mtd@lists.infradead.org \
    --cc=richard.weinberger@gmail.com \
    /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;
as well as URLs for NNTP newsgroup(s).