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: Sun, 18 Oct 2020 22:44:06 +0200	[thread overview]
Message-ID: <cd253730-5742-6449-036a-debdece3d85c@sigma-star.at> (raw)
In-Reply-To: <5efdb785-cd31-1bb1-b1cb-9d213b4d622f@linutronix.de>

On 9/29/20 4:05 PM, Bastian Germann wrote:
>> 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.
>>
> 
> That would be another patch but does not invalidate this one. mtd-utils
> also uses other functions which are deprecated in OpenSSL >= 1.1.0:
> 
> OPENSSL_no_config
> OpenSSL_add_all_digests
> OpenSSL_add_all_algorithms
> EVP_cleanup
> ERR_free_strings
> ERR_load_crypto_strings
> 
> You can yield this list via compiling with -DOPENSSL_API_COMPAT=0x10100000L.
> 

I agree. Given that there is a longer list of other things to take care of anyway
and since it builds just fine with recent OpenSSL on my end as well, I'll just
apply the patch upstream for now.

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

      reply	other threads:[~2020-10-18 20:44 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
2020-09-29 14:05       ` Bastian Germann
2020-10-18 20:44         ` David Oberhollenzer [this message]

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=cd253730-5742-6449-036a-debdece3d85c@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).