[GH-ISSUE #1012] gpg.profile prevents adding ppa #689

Closed
opened 2026-05-05 06:27:03 -06:00 by gitea-mirror · 1 comment
Owner

Originally created by @curiosity-seeker on GitHub (Dec 28, 2016).
Original GitHub issue: https://github.com/netblue30/firejail/issues/1012

The current gpg.profile prevented adding a ppa on Ubuntu 16.04. I got the following errors:

gpg: Fehler beim Erstellen von »/tmp/tmp9y16xntr/secring.gpg«: Fehler beim Öffnen der Datei
gpg: Fehler beim Erstellen von »/tmp/tmp9y16xntr/pubring.gpg«: Fehler beim Öffnen der Datei

After commenting private-tmp this error message vanished but I got a new one:

gpg: Schlüssel C07EE05F von hkp-Server keyserver.ubuntu.com anfordern
?: keyserver.ubuntu.com: Host not found
gpgkeys: HTTP fetch error 7: couldn't connect: Operation not supported

It worked after commenting net none and changing the protocol line to
protocol unix,inet,inet6.

Originally created by @curiosity-seeker on GitHub (Dec 28, 2016). Original GitHub issue: https://github.com/netblue30/firejail/issues/1012 The current gpg.profile prevented adding a ppa on Ubuntu 16.04. I got the following errors: ``` gpg: Fehler beim Erstellen von »/tmp/tmp9y16xntr/secring.gpg«: Fehler beim Öffnen der Datei gpg: Fehler beim Erstellen von »/tmp/tmp9y16xntr/pubring.gpg«: Fehler beim Öffnen der Datei ``` After commenting `private-tmp` this error message vanished but I got a new one: ``` gpg: Schlüssel C07EE05F von hkp-Server keyserver.ubuntu.com anfordern ?: keyserver.ubuntu.com: Host not found gpgkeys: HTTP fetch error 7: couldn't connect: Operation not supported ``` It worked after commenting `net none` and changing the protocol line to `protocol unix,inet,inet6`.
gitea-mirror 2026-05-05 06:27:03 -06:00
  • closed this issue
  • added the
    bug
    label
Author
Owner

@netblue30 commented on GitHub (Dec 29, 2016):

I put the fixes you suggested in. The same fixes went in gpa.profile and gpg-agent.profile.

There is something you need to do manually: remove /usr/local/bin/gpg and /usr/local/bin/gpa files:

sudo rm /usr/local/bin/gpg /usr/local/bin/gpa

We have to assume that gpg infrastructure is rock solid. No amount of sandboxing could ever fix it. So, I removed them from firecfg list, running firejail on them by default is useless.

Thanks for the bug!

<!-- gh-comment-id:269636888 --> @netblue30 commented on GitHub (Dec 29, 2016): I put the fixes you suggested in. The same fixes went in gpa.profile and gpg-agent.profile. There is something you need to do manually: remove /usr/local/bin/gpg and /usr/local/bin/gpa files: ````` sudo rm /usr/local/bin/gpg /usr/local/bin/gpa ````` We have to assume that gpg infrastructure is rock solid. No amount of sandboxing could ever fix it. So, I removed them from firecfg list, running firejail on them by default is useless. Thanks for the bug!
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/firejail#689
No description provided.