All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alexander Kanavin <alexander.kanavin@linux.intel.com>
To: Mark Hatle <mark.hatle@windriver.com>,
	openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 4/4] gstreamer-plugins-bad: replace openssl dependency with nettle for hls plugin
Date: Tue, 8 Aug 2017 20:35:56 +0300	[thread overview]
Message-ID: <c9af037d-bd8f-691c-ec3d-ba17e723805d@linux.intel.com> (raw)
In-Reply-To: <4ae3a694-c172-c4e7-8cf9-97f6cd8507cd@windriver.com>

On 08/08/2017 06:58 PM, Mark Hatle wrote:
> Can we somehow make openssl(10) or nettle a choice when compiling?
> 
> I ask because I've worked on a few systems where people seem to want one
> encryption engine for as much of the system as possible (usually openssl).
> While gstreamer has not been a problem in such systems, I could see it being
> something that would need to be considered.

This would need to be done across all recipes where such choice is 
supported, as a 'preferred crypto engine' distro feature. There's been 
talk of doing this, but I don't remember what was the outcome.

Also, the plugin needs to be ported to 1.1 first, as the choice will 
otherwise be taken away when 1.0 goes EOL.

Alex


  reply	other threads:[~2017-08-08 17:39 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-08 15:30 [PATCH 0/4] Add openssl 1.1 Alexander Kanavin
2017-08-08 15:30 ` [PATCH 1/4] openssl: add a 1.1 version Alexander Kanavin
2017-08-08 15:30 ` [PATCH 2/4] openssh: depend on openssl 1.0 Alexander Kanavin
2017-08-08 15:30 ` [PATCH 3/4] cryptodev-tests: " Alexander Kanavin
2017-08-08 15:30 ` [PATCH 4/4] gstreamer-plugins-bad: replace openssl dependency with nettle for hls plugin Alexander Kanavin
2017-08-08 15:58   ` Mark Hatle
2017-08-08 17:35     ` Alexander Kanavin [this message]
2017-08-08 18:55       ` Mark Hatle
2017-08-08 22:54         ` Andre McCurdy
2017-08-09 11:05         ` Alexander Kanavin
2017-08-08 19:14       ` Burton, Ross
2017-08-08 20:41         ` Mark Hatle

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=c9af037d-bd8f-691c-ec3d-ba17e723805d@linux.intel.com \
    --to=alexander.kanavin@linux.intel.com \
    --cc=mark.hatle@windriver.com \
    --cc=openembedded-core@lists.openembedded.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 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.