mirror of
https://github.com/netblue30/firejail.git
synced 2026-05-15 14:16:14 -06:00
[GH-ISSUE #3129] midori.profile: ad-blocker not working properly #1963
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#1963
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 @Rosika2 on GitHub (Jan 7, 2020).
Original GitHub issue: https://github.com/netblue30/firejail/issues/3129
Hi altogether,
I´ve encountered the following problem: When running the midori web-browser with
firejail midoriit loads the midori.profile which is correct.
Midori runs alright except the issue with the ad-blocker 2.0(0.4.1), which is enabled in midori by default.
The ad-blocker is active but doesn´t seem to function.
Example: when running
firejail midorian then loadinghttps://www.linuxquestions.org/questions/showthread.php?p=6072547#post6072547the respective page is displayed with ads and the ad-blocker shield is green. So the ad-blocker is active but doesn´t seem to work.
When displaying the same page running
firejail --noprofile midorithe page is displayed without ads and the ad-blocker shield is yellow. That´s the way it should be.
So I guess some setting within the midori.profile prevents the ad-blocker from kicking in accurately.
What might be the issue there?
Thanks a lot in advance.
Greetings.
Rosika
P.S.:
@rusty-snake commented on GitHub (Jan 7, 2020):
Probably the ad-blocker works, but has no rules.
We can separate the profile in there parts that can cause this:
include disable-*.inc)caps.drop alltodisable-mnt)@Rosika2 commented on GitHub (Jan 7, 2020):
@rusty-snake:
Thank you so much for your help again.
I tried everything you suggested and it turned out to be
include disable-programs.inc.That´s the only line I had to comment out.
So
# include disable-programs.incenables the pop-up blocker to read the rules. Its icon is yellow and ads aren´t shown.Thanks again for your really fast quality help. It´s much appreciated.
Greetings.
Rosika
@rusty-snake commented on GitHub (Jan 7, 2020):
@Rosika2 in general it is a bad idea to comment
include disable-progams.inc. Here is it not so bad because midori is a whitelisting profile. disable-progams blacklists a lot of program path in $HOME, you could enable it and add a noblacklist command if you know the path. Usejournalctl --grep="blacklist violation" --reverseto see logged access tries to blacklisted paths (from sandboxes withtracelog).@Rosika2 commented on GitHub (Jan 8, 2020):
@rusty-snake:
Hello again and thanks a lot for the additional info.
I looked up my journalctl-entries. What worked for me was the command
journalctl | grep "blacklist violation"which gave me as a resultJan 07 15:28:56 rosika2-Standard-PC-i440FX-PIIX-1996 firejail[2035]: blacklist violation - sandbox 2024, exe midori, syscall access, path /home/rosika2/.cache/midoriThus I got the respective path.
Afterwards I enabled
include disable-progams.incagain and addednoblacklist /home/rosika2/.cache/midori.And it works as desired. The ad-blocker reads the rules and applies them accordingly (yellow symbol) .
Thanks for explaining the inner workings of the profile.
Greetings.
Rosika
@rusty-snake commented on GitHub (Jan 8, 2020):
upsteam
105dce9bba (diff-2d1d56611361d49d41311dab5fe786bb)@Rosika2 thx for your help.