mirror of
https://github.com/netblue30/firejail.git
synced 2026-05-15 14:16:14 -06:00
[GH-ISSUE #6787] Search for .net files in ~/.config/firejail #3372
Labels
No labels
LTS merge
LTS merge
bug
bug
converted-to-discussion
doc-todo
documentation
duplicate
enhancement
file-transfer
firecfg
firejail-in-firejail
firetools
graphics
help wanted
information_old
installation
invalid
modif
moved
needinfo
networking
notabug
notourbug
old-version
overlayfs
packaging
profile-request
pull-request
question
question_old
removal
runtime-permissions
sandbox-ipc
security
stale
wiki
wiki
wontfix
wordpress
workaround
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/firejail#3372
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @minitchoup on GitHub (Jun 18, 2025).
Original GitHub issue: https://github.com/netblue30/firejail/issues/6787
Description:
Firejail considers the ~/.config/firejail directory implicitly for profile files but does not handle .net files in the same manner. This makes it difficult to use custom network configuration files.
Steps to Reproduce:
Create a custom network configuration file with a .net extension, for example, netfilter-for-emacs.net.
Place this file in ~/.config/firejail.
Attempt to use it with Firejail by specifying the relative path.
Expected Behavior:
Firejail should be able to locate and use the .net file in the same way it does for profile files.
Actual Behavior:
Firejail cannot find the .net file and returns an unclear error message.
Environment Information:
Operating System: debian 12
Firejail Version: 0.9.72
@kmk3 commented on GitHub (Jun 18, 2025):
Note that we do not maintain that version of firejail:
Versions other than the latest usually have outdated profiles and may contain
bugs and security vulnerabilities that were fixed in later versions.
See also:
@kmk3 commented on GitHub (Jun 18, 2025):
Yes; this is a known limitation.
Not too long ago I was working on unifying the parsing (in both CLI and
profiles) for the following options:
--profile--include--netfilter--netfilter6Though it was a bit tricky (and I accidentally deleted the changes), so it may
take some time.