public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Jelle van der Waa <jelle@vdwaa.nl>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 1/2] rsa: Fix build with OpenSSL 1.1.x
Date: Tue, 14 Feb 2017 23:14:20 +0100	[thread overview]
Message-ID: <20170214221419.GA3409@gmail.com> (raw)
In-Reply-To: <CALeDE9NtUCfW6tu8nbYvRQ2jidR0wBtAwa=aTsrGU5FjFy+gxw@mail.gmail.com>

On 02/14/17 at 12:43pm, Peter Robinson wrote:
> On Mon, Feb 13, 2017 at 9:57 AM, Peter Robinson <pbrobinson@gmail.com> wrote:
> > On Mon, Feb 13, 2017 at 9:00 AM, Jelle van der Waa <jelle@vdwaa.nl> wrote:
> >> The rsa_st struct has been made opaque in 1.1.x, add forward compatible
> >> code to access the n, e, d members of rsa_struct.
> >>
> >> EVP_MD_CTX_cleanup has been removed in 1.1.x and EVP_MD_CTX_reset should be
> >> called to reinitialise an already created structure.
> >
> > You can add my tested by. Built on Fedora 26 with 1.1.0d. gcc 7 etc.
> 
> Although it needs to be updated for 2017.03rc2 for tools/kwbimage.c as
> it now supports secure boot and I get the following errors on build:

I've created a patch for it here. I'll send it to the list tommorow

http://vps.vdwaa.nl/~jelle/0001-tools-kwbimage-fix-build-with-OpenSSL-1.1.x.patch

-- 
Jelle van der Waa

  reply	other threads:[~2017-02-14 22:14 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-13  9:00 [U-Boot] [PATCH 1/2] rsa: Fix build with OpenSSL 1.1.x Jelle van der Waa
2017-02-13  9:00 ` [U-Boot] [PATCH 2/2] rsa: Fix deprecated warnings for " Jelle van der Waa
2017-02-22  3:59   ` Simon Glass
2017-02-13  9:57 ` [U-Boot] [PATCH 1/2] rsa: Fix build with " Peter Robinson
2017-02-14 12:43   ` Peter Robinson
2017-02-14 22:14     ` Jelle van der Waa [this message]
2017-02-16  1:59 ` Jonathan Gray

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=20170214221419.GA3409@gmail.com \
    --to=jelle@vdwaa.nl \
    --cc=u-boot@lists.denx.de \
    /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