All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: "Andreï V. FOMITCHEV-HERVIEU" <andrei.fomitchevhervieu@getinge.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] package/opkg: enable openssl signature
Date: Wed, 13 Apr 2022 23:08:48 +0200	[thread overview]
Message-ID: <20220413230848.63adde79@windsurf> (raw)
In-Reply-To: <20220413073119.458265-1-andrei.fomitchevhervieu@getinge.com>

Hello Andreï,

On Wed, 13 Apr 2022 09:31:19 +0200
Andreï V. FOMITCHEV-HERVIEU <andrei.fomitchevhervieu@getinge.com> wrote:

> OPKG supports either GPG or OpenSSL signature check. It is already possible
> to enable in buildroot the check of GPG signatures. This patch adds similar
> configuration to enable the OpenSSL signature checks.
> 
> Signed-off-by: Andreï V. FOMITCHEV-HERVIEU <andrei.fomitchevhervieu@getinge.com>
> Change-Id: Id2c76b3cb39ba5eed5bd0bef7648f7970033b87b

Nice to see you here, thanks for the contribution!

However, are you sure it makes sense to support this and use this?
Indeed, opkg has deprecated the usage of openssl for signature. From
opkg's configure.ac:

  AC_MSG_WARN(OpenSSL signature-checking support is depracted and will be \
removed in future releases. Consider using GPGME (--enable-gpg) instead.)

So, it is really sensible to support this?

Thomas
-- 
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  reply	other threads:[~2022-04-13 21:08 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-13  7:31 [Buildroot] [PATCH 1/1] package/opkg: enable openssl signature Andreï V. FOMITCHEV-HERVIEU
2022-04-13 21:08 ` Thomas Petazzoni via buildroot [this message]
2022-04-14  5:53   ` [Buildroot] [EXT] " Andrei FOMITCHEV HERVIEU

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=20220413230848.63adde79@windsurf \
    --to=buildroot@buildroot.org \
    --cc=andrei.fomitchevhervieu@getinge.com \
    --cc=thomas.petazzoni@bootlin.com \
    /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.