From: Paul Barker <paul@pbarker.dev>
To: Markus Volk <f_l_k@t-online.de>,
openembedded-core@lists.openembedded.org
Subject: Re: [oe-core][PATCH 1/5] gcr: initialize libgcrypt from the secret exchange
Date: Sat, 26 Sep 2026 14:53:34 +0100 [thread overview]
Message-ID: <2ce6fc55e1691bf8800a26bf76aab92f440fd676.camel@pbarker.dev> (raw)
In-Reply-To: <20260922092411.262885-1-f_l_k@t-online.de>
On Tue, 2026-09-22 at 11:23 +0200, Markus Volk wrote:
> gnome-shell logs a libgcrypt warning on the first keyring prompt:
>
> Libgcrypt warning: missing initialization - please fix the application
>
> gcr3 initialized libgcrypt from GcrSecretExchange's class_init; gcr 4
> dropped that call, and _gcr_initialize_library() is only reached from
> the certificate, parser and importer paths, never from the prompt path.
> The guard in that function is inverted on top of it, so even when it is
> called the first caller returns without initializing anything.
>
> The secret exchange itself works either way, but libgcrypt then runs
> without the egg secure memory allocators, which puts passwords into
> ordinary swappable heap instead of locked pages.
>
> AI-Generated: Uses Claude Code
> Signed-off-by: Markus Volk <f_l_k@t-online.de>
Hi Marcus,
Has this issue been reported upstream? I see that the patch is
'Pending', which isn't ideal. Given that this affects security we really
should get input from upstream.
Best regards,
--
Paul Barker
prev parent reply other threads:[~2026-09-26 13:53 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-22 9:23 [oe-core][PATCH 1/5] gcr: initialize libgcrypt from the secret exchange Markus Volk
2026-09-22 9:23 ` [oe-core][PATCH 2/5] cpan: survive the Makefile that MakeMaker rebuilds under us Markus Volk
2026-09-26 14:05 ` Paul Barker
2026-09-26 19:03 ` Markus Volk
2026-09-22 9:23 ` [oe-core][PATCH 3/5] spdx_license: give UnknownId a name Markus Volk
2026-09-22 9:23 ` [oe-core][PATCH 4/5] license_finder: normalise license texts before hashing Markus Volk
2026-09-22 9:23 ` [oe-core][PATCH 5/5] go-mod-update-modules: include the generated files from the class Markus Volk
2026-09-22 14:14 ` Antonin Godard
2026-09-23 17:23 ` mrksvolk
2026-09-23 18:03 ` Khem Raj
2026-09-25 11:18 ` Ross Burton
2026-09-25 16:27 ` Markus Volk
2026-09-22 9:33 ` Patchtest results for [oe-core][PATCH 1/5] gcr: initialize libgcrypt from the secret exchange patchtest
2026-09-26 13:53 ` Paul Barker [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=2ce6fc55e1691bf8800a26bf76aab92f440fd676.camel@pbarker.dev \
--to=paul@pbarker.dev \
--cc=f_l_k@t-online.de \
--cc=openembedded-core@lists.openembedded.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