From: Pavel Machek <pavel@nabladev.com>
To: luca.weiss@fairphone.com
Cc: cip-dev@lists.cip-project.org
Subject: Re: [cip-dev] [PATCH 4.19.y-cip 0/4] Backport sign-file,extract-cert patches for OpenSSL 4 compatibility
Date: Tue, 17 Nov 2026 18:51:51 +0100 [thread overview]
Message-ID: <avyUNwowVKWAJDj9@duo.ucw.cz> (raw)
In-Reply-To: <20261112-openssl4-419cip-v1-0-2f56859669bb@fairphone.com>
[-- Attachment #1: Type: text/plain, Size: 674 bytes --]
Hi!
> On Arch Linux the extract-cert tool from 4.19.y-cip doesn't compile
> anymore due to OpenSSL 4 upgrade which removed some APIs used in the
> host tools.
>
> Backport some patches, taken from linux-6.1.y to fix compilation.
>
> Note, this is the first time I'm sending patches to cip-dev, so I hope
> I'm not missing some contribution guidelines.
I believe these are not yet in 5.10, that would be first step.
This is not usual kind of bugfix, nor is it backport from a member
company. Still, I'd not be opposed in taking these, provided 5.10
version is taken first.
Reviewed-by: Pavel Machek <pavel@nabladev.com>
Best regards,
Pavel
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
prev parent reply other threads:[~2026-11-17 17:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-12 12:50 [PATCH 4.19.y-cip 0/4] Backport sign-file,extract-cert patches for OpenSSL 4 compatibility Luca Weiss
2026-11-12 12:50 ` [PATCH 4.19.y-cip 1/4] sign-file,extract-cert: move common SSL helper functions to a header Luca Weiss
2026-11-12 12:50 ` [PATCH 4.19.y-cip 2/4] sign-file,extract-cert: avoid using deprecated ERR_get_error_line() Luca Weiss
2026-11-12 12:50 ` [PATCH 4.19.y-cip 3/4] sign-file,extract-cert: use pkcs11 provider for OPENSSL MAJOR >= 3 Luca Weiss
2026-11-12 12:50 ` [PATCH 4.19.y-cip 4/4] extract-cert: Wrap key_pass with '#ifdef USE_PKCS11_ENGINE' Luca Weiss
2026-11-17 17:51 ` Pavel Machek [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=avyUNwowVKWAJDj9@duo.ucw.cz \
--to=pavel@nabladev.com \
--cc=cip-dev@lists.cip-project.org \
--cc=luca.weiss@fairphone.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.