mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Michael Olbrich <m.olbrich@pengutronix.de>
To: Marco Felsch <m.felsch@pengutronix.de>
Cc: Matthias Fend <matthias.fend@emfend.at>, ptxdist@pengutronix.de
Subject: Re: [ptxdist] [PATCH v2 1/1] libcamera: new package
Date: Wed, 14 Sep 2022 15:06:27 +0200	[thread overview]
Message-ID: <20220914130627.GD28082@pengutronix.de> (raw)
In-Reply-To: <20220914075041.lfflpzk2xzox7req@pengutronix.de>

On Wed, Sep 14, 2022 at 09:50:41AM +0200, Marco Felsch wrote:
> On 22-09-14, Matthias Fend wrote:
> > Thanks for your input. I will also include the additional crypto options.
> > Is the reason for disabling module signing to reduce dependencies on the
> > target, or anything else?
> 
> Yes, it would reduce the dependencies if off. Also this gives the user
> the ability to select the crypto lib which is already used on the
> target. Since the worst case would be to pull a 2nd lib if one already
> have one.
> 
> Don't know if there is some option to select a global crypto provider.
> @Michael is this possible?

So, I like having a choice, because it allows minimizing the number of
crypto libraries. But these is not global default, because it's hard to
implement:
If it's just a default for a choice option, then it must be enabled before
all other packages: The default is is ignored if something is already
enabled. So changing the default has no effect either.

We could also hide the other options when a default is select. But that
means that there is no way to overwrite the default. And sometimes not all
backends have the same features.

Neither version is really desirable, so I never bothered to implement
anything like this.

Michael

-- 
Pengutronix e.K.                           |                             |
Steuerwalder Str. 21                       | http://www.pengutronix.de/  |
31137 Hildesheim, Germany                  | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |



  reply	other threads:[~2022-09-14 13:06 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-11 10:41 [ptxdist] [PATCH v2 0/1] " Matthias Fend
2022-09-11 10:41 ` [ptxdist] [PATCH v2 1/1] " Matthias Fend
2022-09-13 13:53   ` Marco Felsch
2022-09-13 15:31     ` Michael Olbrich
2022-09-14  8:03       ` Marco Felsch
2022-09-14  6:04     ` Matthias Fend
2022-09-14  7:50       ` Marco Felsch
2022-09-14 13:06         ` Michael Olbrich [this message]
2022-09-13 15:24   ` Michael Olbrich
2022-09-14  5:54     ` Matthias Fend
2022-09-14 12:59       ` Michael Olbrich

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=20220914130627.GD28082@pengutronix.de \
    --to=m.olbrich@pengutronix.de \
    --cc=m.felsch@pengutronix.de \
    --cc=matthias.fend@emfend.at \
    --cc=ptxdist@pengutronix.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