From: "Chí-Thanh Christopher Nguyễn" <chithanh@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] [PATCH] eclass/linux-mod.eclass: add module signing support
Date: Sat, 22 Sep 2018 00:59:26 +0200 [thread overview]
Message-ID: <63ca33b7-7663-65bc-24a9-b5f4538dbfa8@gentoo.org> (raw)
In-Reply-To: <1537534680.1635.11.camel@tsoy.me>
Alexander Tsoy schrieb:
>> + sign_binary_path="${KV_OUT_DIR}/scripts/sign-file"
>
> Yet another way to screw up modules building. It relies on some binary
> in the kernel build dir that may break after openssl update (e.g.
> soname change).
Maybe the sign-file application could be packaged, for example as part of
sys-apps/linux-misc-apps.
Best regards,
Chí-Thanh Christopher Nguyễn
next prev parent reply other threads:[~2018-09-21 22:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-21 5:13 [gentoo-dev] [PATCH] eclass/linux-mod.eclass: add module signing support Georgy Yakovlev
2018-09-21 12:58 ` Alexander Tsoy
2018-09-21 22:59 ` Chí-Thanh Christopher Nguyễn [this message]
2018-09-22 2:30 ` Georgy Yakovlev
2018-09-22 2:22 ` Georgy Yakovlev
2018-10-01 8:48 ` [gentoo-dev] [PATCH 1/2] " Georgy Yakovlev
2018-10-01 8:48 ` [gentoo-dev] [PATCH 2/2] profiles: mask module signing for testing Georgy Yakovlev
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=63ca33b7-7663-65bc-24a9-b5f4538dbfa8@gentoo.org \
--to=chithanh@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/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