From: John Kehayias via Guix-patches via <guix-patches@gnu.org>
To: "49957@debbugs.gnu.org" <49957@debbugs.gnu.org>
Cc: Andrew Whatson <whatson@gmail.com>
Subject: [bug#49957] [PATCH] gnu: p11-kit: Fix certificate errors from flatpak apps
Date: Tue, 28 Sep 2021 05:07:54 +0000 [thread overview]
Message-ID: <nBwW7sAMBJXkPw2BGM94-IoOV7pUOtDZyrEVlYVEGMwgwf-Mj3-hLZlVhZxRuee8qQoIf28eWbbfrUpluZUONUbyS--VFJtQPuBpASHpemo=@protonmail.com> (raw)
In-Reply-To: <VlzZOd8ZedUysvC5Qfuhk1TJpPygT_P7tInaIkOuWqInX9Rw0MV9Z4UkML4_Ax8WCpaPzaC_d59tn4z0FdwPxwUhtkWyma9OJUP8WWRgZ6g=@protonmail.com>
For the record, I'm using the beta of Flatpak (installs fine with --with-source transformation), version 1.11.3.
Also, I found a workaround by manually killing the p11-kit server and running a new one that I built with this patch and updated to the latest version. In case this helps anyone, I ran with the parameters Flatpak tries to launch:
p11-kit server --sh -n /run/user/1000/.flatpak-helper/pkcs11-flatpak-#### --provider p11-kit-trust.so "pkcs11:model=p11-kit-trust?write-protected=yes"
where the -n argument #### came from trying to run a Flatpak app and seeing it fail not finding the p11-kit server at that socket. Probably you can do this more easily by forcing Flatpak when it first runs to use the fixed p11-kit version (through a patch in Flatpak or some environment setting? or what the system starts?). But with p11-kit server already running for me, this did the trick for testing.
next prev parent reply other threads:[~2021-09-28 5:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-09 14:14 [bug#49957] [PATCH] gnu: p11-kit: Fix certificate errors from flatpak apps Andrew Whatson
2021-09-28 2:26 ` John Kehayias via Guix-patches via
2021-09-28 5:07 ` John Kehayias via Guix-patches via [this message]
2021-10-25 19:13 ` bug#49957: " Ludovic Courtès
2021-10-25 19:33 ` [bug#49957] " John Kehayias via Guix-patches via
2021-10-27 14:27 ` Ludovic Courtès
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='nBwW7sAMBJXkPw2BGM94-IoOV7pUOtDZyrEVlYVEGMwgwf-Mj3-hLZlVhZxRuee8qQoIf28eWbbfrUpluZUONUbyS--VFJtQPuBpASHpemo=@protonmail.com' \
--to=guix-patches@gnu.org \
--cc=49957@debbugs.gnu.org \
--cc=john.kehayias@protonmail.com \
--cc=whatson@gmail.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).