mirror of
https://github.com/netblue30/firejail.git
synced 2026-05-15 14:16:14 -06:00
[GH-ISSUE #4421] Fix new profiles after [no]deny / [no]allow revert #2662
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#2662
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 @adgross on GitHub (Jul 26, 2021).
Original GitHub issue: https://github.com/netblue30/firejail/issues/4421
Files from the commit
a25e4a1011still uses deny / nodeny and allow / noallow after merging the revert8b50039a1f.The revert commit
f43382f1e9is older than these profiles, while the merge itself happened later, so the revert missed the new files.Affected files:
@rusty-snake commented on GitHub (Jul 26, 2021):
And #4407.
@rusty-snake commented on GitHub (Jul 28, 2021):
2e4d52ec60@kmk3 commented on GitHub (Jul 29, 2021):
Thanks everyone for catching and fixing this. I wasn't sure how/when to handle
PRs with profile changes made between the original commit (
fe0f975) and themerge of the revert (
f43382f), so I had just set it aside. But it looks likeeverything has been caught indeed:
And the remaining open PRs seem to be unaffected as well.
Nice to see it all sorted out.
Link to the revert PR for cross-reference: #4410.
@Fred-Barclay commented on GitHub (Jul 30, 2021):
Ha I ran across the files by accident in that commit - thanks to @adgross for catching these as well!