From: Stefan Strogin <stefan.strogin@gmail.com>
To: Lucas De Marchi <lucas.demarchi@intel.com>
Cc: linux-modules@vger.kernel.org, ykaliuta@redhat.com
Subject: Re: [PATCH] libkmod-signature: use PKCS7 for LibreSSL or older OpenSSL
Date: Fri, 1 Mar 2019 07:37:08 +0200 [thread overview]
Message-ID: <0916b8bc-383d-bcd4-432c-a1ec19db4e80@gmail.com> (raw)
In-Reply-To: <6633f8d3-c9d6-02d4-6226-204038df1f81@gmail.com>
Hi Lucas,
Is there any chance for accepting this patch?
Or could you tell me how it can be reworked so that modinfo would support PKCS#7
(and LibreSSL)?
--
Stefan
On 15/02/2019 15:30, Stefan Strogin wrote:
> On 15/02/2019 10:04, Lucas De Marchi wrote:
>>
>> ooh, this ifdef is messy. Why do we want both libressl and openssl? What
>> distro is requiring that?
>
> Well, in the kernel in scripts/sign-file.c the same ifdefs are used.
>
> Every distro that tries to support LibreSSL requires that. I know at least
> Gentoo [1], Alpine and Void.
>
>> if in the end we end up with ifdefs for N different libs I'd rather just
>> add the implementation in kmod itself or convince kernel guys to just
>> fill out the struct they are supposed to fill.
>
> If you don't like ifdefs at all I would say that CMS is not needed. CMS and
> PKCS#7 formats are very similar. CMS is newer but is as much as possible
> backward compatible [2], but PKCS#7 is better supported. PKCS#7 has all the same
> fields that are used when a kernel module is signed using CMS (and otherwise).
> For example I can sign a module using OpenSSL-1.1.1 and CMS (even with hashes
> other than sha1) and read its signing information with modinfo and PKCS#7 on a
> system with LibreSSL, and otherwise.
>
> So we can just replace CMS with PKCS#7 in fill_pkcs7().
>
> [1] https://bugs.gentoo.org/677960
> [2] https://tools.ietf.org/html/rfc5652#section-1.1
>
> --
> Stefan
>
prev parent reply other threads:[~2019-03-01 5:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-15 4:13 [PATCH] libkmod-signature: use PKCS7 for LibreSSL or older OpenSSL Stefan Strogin
2019-02-15 8:04 ` Lucas De Marchi
2019-02-15 13:30 ` Stefan Strogin
2019-03-01 5:37 ` Stefan Strogin [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=0916b8bc-383d-bcd4-432c-a1ec19db4e80@gmail.com \
--to=stefan.strogin@gmail.com \
--cc=linux-modules@vger.kernel.org \
--cc=lucas.demarchi@intel.com \
--cc=ykaliuta@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).