All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Andre McCurdy <armccurdy@gmail.com>
Cc: Otavio Salvador <otavio@ossystems.com.br>,
	OpenEmbedded Core Mailing List
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH v2] openssl: Use the c_rehash shell re-implementation for target
Date: Mon, 18 Mar 2019 23:56:44 +0000	[thread overview]
Message-ID: <5ebe88235599c79c6f125e327bf321f9e3c30700.camel@linuxfoundation.org> (raw)
In-Reply-To: <CAJ86T=U0NLArgbpFWt_FooB0H9sTYxyqC345ZMftFDXezJfV9Q@mail.gmail.com>

On Mon, 2019-03-18 at 16:52 -0700, Andre McCurdy wrote:
> On Mon, Mar 18, 2019 at 4:35 PM Richard Purdie
> <richard.purdie@linuxfoundation.org> wrote:
> > I went to have a look at how this upstream C utility was going and
> > found that they've moved to github issues and there is no such
> > issue
> > open.
> 
> It's already been implemented and is present in openssl 1.1.0:
> 
>   https://www.openssl.org/docs/man1.1.0/man1/rehash.html

Great, it felt like I was missing something!

Otavio: Why do we need c_rehash on target at all, can we use rehash?

Cheers,

Richard



  reply	other threads:[~2019-03-18 23:56 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-18 13:36 [PATCH v2] openssl: Use the c_rehash shell re-implementation for target Otavio Salvador
2019-03-18 14:53 ` Alexander Kanavin
2019-03-18 16:00   ` Otavio Salvador
2019-03-18 16:09     ` Alexander Kanavin
2019-03-18 23:18       ` Richard Purdie
2019-03-18 23:26         ` Otavio Salvador
2019-03-18 23:34 ` Richard Purdie
2019-03-18 23:52   ` Andre McCurdy
2019-03-18 23:56     ` Richard Purdie [this message]
2019-03-19  0:10       ` Otavio Salvador

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=5ebe88235599c79c6f125e327bf321f9e3c30700.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=armccurdy@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=otavio@ossystems.com.br \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.