All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrei FOMITCHEV HERVIEU <andrei.fomitchevhervieu@getinge.com>
To: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Cc: "buildroot@buildroot.org" <buildroot@buildroot.org>
Subject: Re: [Buildroot] [EXT] Re: [PATCH 1/1] package/opkg: enable openssl signature
Date: Thu, 14 Apr 2022 05:53:35 +0000	[thread overview]
Message-ID: <AM0PR02MB5427EEEF5C87B7EDC15E85ABECEF9@AM0PR02MB5427.eurprd02.prod.outlook.com> (raw)
In-Reply-To: <20220413230848.63adde79@windsurf>

Hello Thomas,

Thank you for the point. Maybe you remember, I (still) use the version 2021.02 of buildroot and this version integrates the version 0.4.2 of OPKG. The quoted comment in OPKG sources was introduced in v0.4.5 and the reason is "relatively unused feature" of OpenSSL signatures (https://groups.google.com/g/opkg-devel/c/drqw5_HuXuU).
So I agree, the OPKG project plans make my patch to buildroot useless

Best regards

De : Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Envoyé : mercredi 13 avril 2022 23:09
À : Andrei FOMITCHEV HERVIEU <andrei.fomitchevhervieu@getinge.com>
Cc : buildroot@buildroot.org
Objet : [EXT] Re: [Buildroot] [PATCH 1/1] package/opkg: enable openssl signature

CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe.

Hello Andreï,

On Wed, 13 Apr 2022 09:31:19 +0200
Andreï V. FOMITCHEV-HERVIEU <mailto: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 <mailto: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
This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to which they are addressed. If you have received this email in error please notify the system manager. This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. If you are not the intended recipient you are notified that disclosing, copying, distributing or taking any action in reliance on the contents of this information is strictly prohibited.
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

      reply	other threads:[~2022-04-14  5:53 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
2022-04-14  5:53   ` Andrei FOMITCHEV HERVIEU [this message]

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=AM0PR02MB5427EEEF5C87B7EDC15E85ABECEF9@AM0PR02MB5427.eurprd02.prod.outlook.com \
    --to=andrei.fomitchevhervieu@getinge.com \
    --cc=buildroot@buildroot.org \
    --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.