mirror of
https://github.com/netblue30/firejail.git
synced 2026-05-15 14:16:14 -06:00
[GH-ISSUE #686] detecting malware? #471
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#471
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 @xahare on GitHub (Aug 5, 2016).
Original GitHub issue: https://github.com/netblue30/firejail/issues/686
Can firejail log policy violations or otherwise alert the user to bugs or malicious activity?
@manevich commented on GitHub (Aug 5, 2016):
See
--tracelogoption for logging. But note - this is implemented usingLD_PRELOADand it's not too hard to get round for malware, AFAIK.@manevich commented on GitHub (Aug 6, 2016):
Actually
/etc/ld.so.preload. (I was answering late at night)@chiraag-nataraj commented on GitHub (Aug 9, 2016):
@xahare it's easier to just whitelist the behaviors you want the program to have access to than to try to heuristically detect whether it's acting maliciously. For example, I quarantine my browser (Firefox) to my Downloads directory (and its configuration files) and a
private-tmpas well as limit the binaries and files in /etc that it has access to. I also disable the root user, limit which syscalls it has access to, and don't give it access to a shell (it doesn't need one). This is in addition to using addons like uMatrix to limit the number and scope of scripts that run on a page. Basically, my point is that it's easier (although quite tedious) to think about the behaviors you want and to whitelist them than to try to figure out if some specific behavior you saw is malicious (even if you're the one trawling through the logs - andfirejailhas pretty detailed logging).@xahare commented on GitHub (Aug 11, 2016):
@chiraag-nataraj that sounds awsome! can you gist your firefox setup?
the point of this isn't better protection. its knowing when somethings wrong that you would otherwise miss.
@chiraag-nataraj commented on GitHub (Aug 11, 2016):
So my profile is attached here (rename it to firefox.profile)
The list of privacy/security addons I use in Firefox (mainly for privacy, but they also provide some added security):
Decentraleyes (https://addons.mozilla.org/en-US/firefox/addon/decentraleyes/)
Disconnect (https://addons.mozilla.org/en-US/firefox/addon/disconnect/)
RequestPolicy (https://addons.mozilla.org/en-US/firefox/addon/requestpolicy-continued/)
Self-Destructing Cookies (https://addons.mozilla.org/en-US/firefox/addon/self-destructing-cookies/)
uBlock Origin (https://addons.mozilla.org/en-US/firefox/addon/ublock-origin/)
uMatrix (https://addons.mozilla.org/en-US/firefox/addon/umatrix/)
Fair enough 😄 I just happen to believe that a whitelist of actions along with a restrictive firewall can generally limit any damage that may occur 😉