All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jussi Kukkonen <jussi.kukkonen@intel.com>
To: Mark Hatle <mark.hatle@windriver.com>
Cc: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 4/4] xserver-xorg: Add PACKAGECONFIG for crypto libraries
Date: Wed, 10 Feb 2016 10:25:08 +0200	[thread overview]
Message-ID: <CAHiDW_GPu1LrmHnBVCqsCXm7MGCxwESoejb57zaqSG1HQAjwWw@mail.gmail.com> (raw)
In-Reply-To: <56BA2A15.2060706@windriver.com>

[-- Attachment #1: Type: text/plain, Size: 2413 bytes --]

On 9 February 2016 at 20:04, Mark Hatle <mark.hatle@windriver.com> wrote:

> On 2/9/16 11:54 AM, Khem Raj wrote:
> >
> >> On Feb 9, 2016, at 1:39 AM, Nicolas Dechesne <
> nicolas.dechesne@linaro.org> wrote:
> >>
> >> On Tue, Feb 9, 2016 at 10:24 AM, Jussi Kukkonen
> >> <jussi.kukkonen@intel.com> wrote:
> >>> Default to libcrypto (openssl) as before.
> >>>
> >>> Signed-off-by: Jussi Kukkonen <jussi.kukkonen@intel.com>
> >>
> >> Looks good to me. this is the same implementation I used in the mesa
> >> patch.. so we need to make sure that any review feedback is applied to
> >> both before merging the too,
> >
> > since its spans multiple recipes would it be better to control it with
> > a global knob instead of packageconfig.
>
> I'm not sure it makes sense in -this- case..  but I've more then once
> thought
> that it would be nice for a global distro "this is the preferred crypto
> engine"
> setting.
>
> That way you could do things like default to openssl, libgcrypt, libnss,
> etc..
> whatever is appropriate for the system you are building.  It wouldn't
> promise
> that everything would just use that crypto backend, but things that could
> -- should.


I was wondering if something like this was possible as well: that's how I
got into reviewing the reverse dependencies of openssl & gnutls.

There are some cases that might make this effort not worth the trouble:
SHA1 is easy and switching implementations is something upstream projects
want to support but with e.g. TLS it is not always so: An example is
glib-networking with only gnutls for TLS support*.

Jussi


*) There's a "wip/openssl" branch of glib-networking so this might get
fixed in future releases .



(This is certainly a more extensive patch then what's being discussed
> here..)
>
> --Mark
>
> >> should we get any review feedback.. but
> >> in any case:
> >>
> >> Reviewed-by: Nicolas Dechesne <nicolas.dechesne@linaro.org>
> >> --
> >> _______________________________________________
> >> Openembedded-core mailing list
> >> Openembedded-core@lists.openembedded.org
> >> http://lists.openembedded.org/mailman/listinfo/openembedded-core
> >
> >
> >
>
> --
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core
>

[-- Attachment #2: Type: text/html, Size: 3961 bytes --]

  reply	other threads:[~2016-02-10  8:25 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-09  9:13 [PATCH 0/4] Crypto dependency fixes Jussi Kukkonen
2016-02-09  9:24 ` [PATCH 1/4] systemd: Don't depend on gcrypt unnecessarily Jussi Kukkonen
2016-02-09  9:24 ` [PATCH 2/4] wpa-supplicant: Only depend on libgcrypt when needed Jussi Kukkonen
2016-02-09  9:24 ` [PATCH 3/4] libsoup-2.4: Remove unnecessary gnutls dependency Jussi Kukkonen
2016-02-09  9:24 ` [PATCH 4/4] xserver-xorg: Add PACKAGECONFIG for crypto libraries Jussi Kukkonen
2016-02-09  9:39   ` Nicolas Dechesne
2016-02-09 17:54     ` Khem Raj
2016-02-09 17:58       ` Burton, Ross
2016-02-09 19:04         ` Khem Raj
2016-02-09 19:41           ` Nicolas Dechesne
2016-02-09 21:21             ` Khem Raj
2016-02-09 18:04       ` Mark Hatle
2016-02-10  8:25         ` Jussi Kukkonen [this message]
2016-02-10 14:44           ` 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=CAHiDW_GPu1LrmHnBVCqsCXm7MGCxwESoejb57zaqSG1HQAjwWw@mail.gmail.com \
    --to=jussi.kukkonen@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.