[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"project-6357":3},{"id":4,"name":5,"fullName":6,"owner":7,"repo":5,"description":8,"homepage":9,"htmlUrl":10,"language":11,"languages":10,"totalLinesOfCode":10,"stars":12,"forks":13,"watchers":14,"openIssues":15,"contributorsCount":16,"subscribersCount":16,"size":16,"stars1d":17,"stars7d":18,"stars30d":19,"stars90d":16,"forks30d":16,"starsTrendScore":20,"compositeScore":21,"rankGlobal":10,"rankLanguage":10,"license":22,"archived":23,"fork":23,"defaultBranch":24,"hasWiki":25,"hasPages":23,"topics":26,"createdAt":10,"pushedAt":10,"updatedAt":27,"readmeContent":28,"aiSummary":29,"trendingCount":16,"starSnapshotCount":16,"syncStatus":17,"lastSyncTime":30,"discoverSource":31},6357,"firejail","netblue30\u002Ffirejail","netblue30","Linux namespaces and seccomp-bpf sandbox","https:\u002F\u002Ffirejail.wordpress.com",null,"C",7462,667,93,508,0,2,22,106,14,39.47,"GNU General Public License v2.0",false,"master",true,[],"2026-06-12 02:01:18","# Firejail\n\n[![Build (GitLab)](https:\u002F\u002Fgitlab.com\u002FFirejail\u002Ffirejail_ci\u002Fbadges\u002Fmaster\u002Fpipeline.svg)](https:\u002F\u002Fgitlab.com\u002FFirejail\u002Ffirejail_ci\u002Fpipelines)\n[![Build (GitHub)](https:\u002F\u002Fgithub.com\u002Fnetblue30\u002Ffirejail\u002Fworkflows\u002FBuild\u002Fbadge.svg)](https:\u002F\u002Fgithub.com\u002Fnetblue30\u002Ffirejail\u002Factions?query=workflow%3ABuild)\n[![Build-extra](https:\u002F\u002Fgithub.com\u002Fnetblue30\u002Ffirejail\u002Fworkflows\u002FBuild-extra\u002Fbadge.svg)](https:\u002F\u002Fgithub.com\u002Fnetblue30\u002Ffirejail\u002Factions?query=workflow%3ABuild-extra)\n[![Test](https:\u002F\u002Fgithub.com\u002Fnetblue30\u002Ffirejail\u002Fworkflows\u002FTest\u002Fbadge.svg)](https:\u002F\u002Fgithub.com\u002Fnetblue30\u002Ffirejail\u002Factions?query=workflow%3ATest)\n[![Check-C](https:\u002F\u002Fgithub.com\u002Fnetblue30\u002Ffirejail\u002Fworkflows\u002FCheck-C\u002Fbadge.svg)](https:\u002F\u002Fgithub.com\u002Fnetblue30\u002Ffirejail\u002Factions?query=workflow%3ACheck-C)\n[![Check-Profiles](https:\u002F\u002Fgithub.com\u002Fnetblue30\u002Ffirejail\u002Fworkflows\u002FCheck-Profiles\u002Fbadge.svg)](https:\u002F\u002Fgithub.com\u002Fnetblue30\u002Ffirejail\u002Factions?query=workflow%3ACheck-Profiles)\n[![Check-Python](https:\u002F\u002Fgithub.com\u002Fnetblue30\u002Ffirejail\u002Fworkflows\u002FCheck-Python\u002Fbadge.svg)](https:\u002F\u002Fgithub.com\u002Fnetblue30\u002Ffirejail\u002Factions?query=workflow%3ACheck-Python)\n[![Codespell](https:\u002F\u002Fgithub.com\u002Fnetblue30\u002Ffirejail\u002Fworkflows\u002FCodespell\u002Fbadge.svg)](https:\u002F\u002Fgithub.com\u002Fnetblue30\u002Ffirejail\u002Factions?query=workflow%3ACodespell)\n[![Packaging status (Repology)](https:\u002F\u002Frepology.org\u002Fbadge\u002Ftiny-repos\u002Ffirejail.svg)](https:\u002F\u002Frepology.org\u002Fproject\u002Ffirejail\u002Fversions)\n\nFirejail is a lightweight security tool intended to protect a Linux system by\nsetting up a restricted environment for running (potentially untrusted)\napplications.\n\nMore specifically, it is an SUID sandbox program that reduces the risk of\nsecurity breaches by using Linux namespaces, seccomp-bpf and Linux\ncapabilities.  It allows a process and all its descendants to have their own\nprivate view of the globally shared kernel resources, such as the network\nstack, process table and mount table.  Firejail can work in an SELinux or\nAppArmor environment, and it is integrated with Linux Control Groups.\n\nWritten in C with virtually no dependencies, the software runs on any Linux\ncomputer with a 3.x kernel version or newer.  It can sandbox any type of\nprocesses: servers, graphical applications, and even user login sessions.  The\nsoftware includes sandbox profiles for a number of more common Linux programs,\nsuch as Mozilla Firefox, Chromium, VLC, Transmission etc.\n\nThe sandbox is lightweight, the overhead is low.  There are no complicated\nconfiguration files to edit, no socket connections open, no daemons running in\nthe background.  All security features are implemented directly in Linux kernel\nand available on any Linux computer.\n\n## Videos\n\n\u003Ctable>\n\u003Ctr>\n\n\u003Ctd>\n\u003Ca href=\"https:\u002F\u002Fodysee.com\u002F@netblue30:9\u002Finstall\" target=\"_blank\">\n\u003Cimg src=\"https:\u002F\u002Fthumbs.odycdn.com\u002Ff19bcfa08c2b35658dc18f4e2fd63f3f.webp\"\nalt=\"Quick Start\" width=\"240\" height=\"142\" border=\"10\" \u002F>\n\u003Cbr\u002F>Quick Start\n\u003C\u002Fa>\n\u003C\u002Ftd>\n\n\u003Ctd>\n\u003Ca href=\"https:\u002F\u002Fodysee.com\u002F@netblue30:9\u002Ffirefox\" target=\"_blank\">\n\u003Cimg src=\"https:\u002F\u002Fthumbs.odycdn.com\u002Facf4b1c66737feb97640fb1d28a7daa6.png\"\nalt=\"Advanced Browser Security\" width=\"240\" height=\"142\" border=\"10\" \u002F>\n\u003Cbr\u002F>Advanced Browser Security\n\u003C\u002Fa>\n\u003C\u002Ftd>\n\n\u003Ctd>\n\u003Ca href=\"https:\u002F\u002Fodysee.com\u002F@netblue30:9\u002Ftor\" target=\"_blank\">\n\u003Cimg src=\"https:\u002F\u002Fthumbs.odycdn.com\u002Ff6aa82bd7b86b2f17caed03ccb870d2b.webp\"\nalt=\"Tor Browser Security\" width=\"240\" height=\"142\" border=\"10\" \u002F>\n\u003Cbr\u002F>Tor Browser Security\n\u003C\u002Fa>\n\u003C\u002Ftd>\n\n\u003C\u002Ftr>\n\u003C\u002Ftable>\n\n## Links\n\n* Project webpage: \u003Chttps:\u002F\u002Ffirejail.wordpress.com\u002F>\n* IRC: \u003Chttps:\u002F\u002Fweb.libera.chat\u002F#firejail>\n* Download and Installation: \u003Chttps:\u002F\u002Ffirejail.wordpress.com\u002Fdownload-2\u002F>\n* Features: \u003Chttps:\u002F\u002Ffirejail.wordpress.com\u002Ffeatures-3\u002F>\n* Documentation: \u003Chttps:\u002F\u002Ffirejail.wordpress.com\u002Fdocumentation-2\u002F>\n* FAQ: \u003Chttps:\u002F\u002Fgithub.com\u002Fnetblue30\u002Ffirejail\u002Fwiki\u002FFrequently-Asked-Questions>\n* Wiki: \u003Chttps:\u002F\u002Fgithub.com\u002Fnetblue30\u002Ffirejail\u002Fwiki>\n* GitHub Actions: \u003Chttps:\u002F\u002Fgithub.com\u002Fnetblue30\u002Ffirejail\u002Factions>\n* GitLab CI: \u003Chttps:\u002F\u002Fgitlab.com\u002FFirejail\u002Ffirejail_ci\u002Fpipelines>\n* Debian CI: \u003Chttps:\u002F\u002Fsalsa.debian.org\u002Freiner\u002Ffirejail>\n* Debian Package Tracker: \u003Chttps:\u002F\u002Ftracker.debian.org\u002Fpkg\u002Ffirejail>\n* Ubuntu PPA: \u003Chttps:\u002F\u002Flaunchpad.net\u002F~deki\u002F+archive\u002Fubuntu\u002Ffirejail>\n* Video Channel: \u003Chttps:\u002F\u002Fodysee.com\u002F@netblue30:9?order=new>\n* Backup Video Channel: \u003Chttps:\u002F\u002Fwww.bitchute.com\u002Fprofile\u002FJSBsA1aoQVfW\u002F>\n\n## Security vulnerabilities\n\nSee [SECURITY.md](SECURITY.md).\n\n## Installing\n\nFor the supported versions, see [SECURITY.md](SECURITY.md).\n\n### Debian\n\nNote: The versions from Debian stable and backports are likely to be outdated,\nso currently we recommend either downloading and installing the .deb package\nfrom the latest release:\n\n* \u003Chttps:\u002F\u002Fgithub.com\u002Fnetblue30\u002Ffirejail\u002Freleases\u002Flatest>\n\nOr [building from source](#building).\n\n\u003Cdetails>\n\u003Csummary>Old instructions\u003C\u002Fsummary>\n\nDebian stable (bullseye): We recommend to use the\n[backports](https:\u002F\u002Fpackages.debian.org\u002Fbullseye-backports\u002Ffirejail) package.\n\n\u003C\u002Fdetails>\n\n### Ubuntu\n\nNote: The versions from the distribution and PPA are likely to be outdated, so\ncurrently we recommend either downloading and installing the .deb package from\nthe latest release:\n\n* \u003Chttps:\u002F\u002Fgithub.com\u002Fnetblue30\u002Ffirejail\u002Freleases\u002Flatest>\n\nOr [building from source](#building).\n\n\u003Cdetails>\n\u003Csummary>Old instructions\u003C\u002Fsummary>\n\nNote: The PPA recommendation is mainly for firejail itself; it should be fine\nto install firetools and firejail-related tools directly from the distribution\nif they are not in the PPA as they tend to be updated less frequently.\n\nFor Ubuntu 18.04+ and derivatives (such as Linux Mint), users are **strongly\nadvised** to use the\n[PPA](https:\u002F\u002Flaunchpad.net\u002F~deki\u002F+archive\u002Fubuntu\u002Ffirejail).\n\nHow to add and install from the PPA:\n\n```sh\nsudo add-apt-repository ppa:deki\u002Ffirejail\nsudo apt-get update\nsudo apt-get install firejail firejail-profiles\n```\n\nReason: The firejail package for Ubuntu 20.04 has been left vulnerable to\nCVE-2021-26910 for months after a patch for it was posted on Launchpad:\n\n* [CVE-2021-26910](https:\u002F\u002Fgithub.com\u002Fadvisories\u002FGHSA-2q4h-h5jp-942w)\n* [firejail version in Ubuntu 20.04 LTS is vulnerable to\n  CVE-2021-26910](https:\u002F\u002Fbugs.launchpad.net\u002Fubuntu\u002F+source\u002Ffirejail\u002F+bug\u002F1916767)\n\nSee also \u003Chttps:\u002F\u002Fwiki.ubuntu.com\u002FSecurityTeam\u002FFAQ>:\n\n> What software is supported by the Ubuntu Security team?\n>\n> Ubuntu is currently divided into four components: main, restricted, universe\n> and multiverse.  All binary packages in main and restricted are supported by\n> the Ubuntu Security team for the life of an Ubuntu release, while binary\n> packages in universe and multiverse are supported by the Ubuntu community.\n\nAdditionally, the PPA version is likely to be more recent and to contain more\nprofile fixes.\n\nSee the following discussions for details:\n\n* [Should I keep using the version of firejail available in my distro\n  repos?](https:\u002F\u002Fgithub.com\u002Fnetblue30\u002Ffirejail\u002Fdiscussions\u002F4666)\n* [How to install the latest version on Ubuntu and\n  derivatives](https:\u002F\u002Fgithub.com\u002Fnetblue30\u002Ffirejail\u002Fdiscussions\u002F4663)\n\n\u003C\u002Fdetails>\n\n### Other\n\nFirejail is available in multiple Linux distributions:\n\n\u003Cdetails>\n\u003Csummary>Repology\u003C\u002Fsummary>\n\u003Cp>\n\n[![Packaging status (Repology)](https:\u002F\u002Frepology.org\u002Fbadge\u002Fvertical-allrepos\u002Ffirejail.svg)](https:\u002F\u002Frepology.org\u002Fproject\u002Ffirejail\u002Fversions)\n\n\u003C\u002Fp>\n\u003C\u002Fdetails>\n\nOther than the [aforementioned exceptions](#installing), as long as your\ndistribution provides a [supported version](SECURITY.md) of firejail, it's\ngenerally a good idea to install it from the distribution.\n\nThe version can be checked with `firejail --version` after installing.\n\nYou can also install one of the [released\npackages](https:\u002F\u002Fgithub.com\u002Fnetblue30\u002Ffirejail\u002Freleases).\n\n## Building\n\nInstructions for building and installing the current development version from\nsource.\n\nIt is recommended to use the distribution-specific instructions below when\napplicable, as they generate native packages, which should make integration\nwith the rest of the system and package management easier.\n\nFor other distributions, see the [generic instructions](#generic).\n\nSee also [.gitlab-ci.yml](.gitlab-ci.yml) for how distribution-specific builds\nare done in CI.\n\n### Arch\n\nNote: The AUR package is not maintained by us.\n\nInstall [firejail-git](https:\u002F\u002Faur.archlinux.org\u002Fpackages\u002Ffirejail-git) from\nthe AUR.\n\nExample:\n\n```sh\nyay -S firejail-git\n```\n\n### Debian\n\nFor Debian, Ubuntu and derivatives:\n\nNote: Any .\u002Fconfigure flags should be passed to [`mkdeb.sh`](mkdeb.sh)\n(such as `.\u002Fmkdeb.sh --enable-foo`).\n\n```sh\nsudo apt-get update -qy\nsudo apt-get install -qy \\\n  git build-essential fakeroot lintian libapparmor-dev pkg-config gawk\ngit clone 'https:\u002F\u002Fgithub.com\u002Fnetblue30\u002Ffirejail.git' &&\ncd firejail &&\n.\u002Fconfigure &&\nmake dist &&\n.\u002Fmkdeb.sh &&\nsudo dpkg -i .\u002F*.deb &&\nmake installcheck\n```\n\n### Fedora\n\nFor Fedora and derivatives:\n\nNote: Any .\u002Fconfigure flags should be passed to [`mkrpm.sh`](platform\u002Frpm\u002Fmkrpm.sh)\n(such as `.\u002Fplatform\u002Frpm\u002Fmkrpm.sh --enable-foo`).\n\n```sh\nsudo dnf update -y\nsudo dnf install -y rpm-build gcc make\ngit clone 'https:\u002F\u002Fgithub.com\u002Fnetblue30\u002Ffirejail.git' &&\ncd firejail &&\n.\u002Fconfigure &&\nmake dist &&\n.\u002Fplatform\u002Frpm\u002Fmkrpm.sh &&\nsudo rpm -i .\u002F*.rpm &&\nmake installcheck\n```\n\n### Generic\n\nGeneric build\u002Finstall instructions:\n\n```sh\ngit clone 'https:\u002F\u002Fgithub.com\u002Fnetblue30\u002Ffirejail.git' &&\ncd firejail &&\n.\u002Fconfigure &&\nmake -j \"$(nproc)\" &&\nsudo make install-strip &&\nmake installcheck\n```\n\nOn Debian\u002FUbuntu you will need to install git and gcc.\n\nTo build with AppArmor support (which is usually used on Debian, Ubuntu,\nopenSUSE and derivatives), install the AppArmor development libraries and\npkg-config and use the `--enable-apparmor` .\u002Fconfigure option:\n\n```sh\nsudo apt-get install git build-essential libapparmor-dev pkg-config gawk\n```\n\nTo build with SELinux support (which is usually used on Fedora, RHEL and\nderivatives), install libselinux1-dev (libselinux-devel on Fedora) and use the\n`--enable-selinux` .\u002Fconfigure option.\n\nDetailed information on using firejail from git is available on the\n[wiki](https:\u002F\u002Fgithub.com\u002Fnetblue30\u002Ffirejail\u002Fwiki\u002FUsing-firejail-from-git).\n\n## Running the sandbox\n\nNote: Make sure to use the full path to the program (for example, `firejail\n\u002Fusr\u002Fbin\u002Ffirefox` instead of `firejail firefox`) to avoid potential\nfirejail-in-firejail issues (see\n[#2877](https:\u002F\u002Fgithub.com\u002Fnetblue30\u002Ffirejail\u002Fissues\u002F2877)).\n\nTo start the sandbox, prefix your command with `firejail`:\n\n```sh\nfirejail \u002Fusr\u002Fbin\u002Ffirefox            # starting Mozilla Firefox\nfirejail \u002Fusr\u002Fbin\u002Ftransmission-gtk   # starting Transmission BitTorrent\nfirejail \u002Fusr\u002Fbin\u002Fvlc                # starting VideoLAN Client\nsudo firejail \u002Fetc\u002Finit.d\u002Fnginx start\n```\n\nRun `firejail --list` in a terminal to list all active sandboxes.  Example:\n\n```console\n$ firejail --list\n1617:netblue:\u002Fusr\u002Fbin\u002Ffirejail \u002Fusr\u002Fbin\u002Ffirefox-esr\n7719:netblue:\u002Fusr\u002Fbin\u002Ffirejail \u002Fusr\u002Fbin\u002Ftransmission-qt\n7779:netblue:\u002Fusr\u002Fbin\u002Ffirejail \u002Fusr\u002Fbin\u002Fgalculator\n7874:netblue:\u002Fusr\u002Fbin\u002Ffirejail \u002Fusr\u002Fbin\u002Fvlc --started-from-file file:\u002F\u002F\u002Fhome\u002Fnetblue\u002Ffirejail-whitelist.mp4\n7916:netblue:firejail --list\n```\n\n## Desktop integration\n\nIntegrate your sandbox into your desktop by running the following two commands:\n\n```sh\nfirecfg --fix-sound\nsudo firecfg\n```\n\nThe first command solves some shared memory\u002FPID namespace bugs in PulseAudio\nsoftware prior to version 9.  The second command integrates Firejail into your\ndesktop.  You would need to logout and login back to apply PulseAudio changes.\n\nStart your programs the way you are used to: desktop manager menus, file\nmanager, desktop launchers.\n\nThe integration applies to any program supported by default by Firejail.  There\nare over 900 default applications in the current Firejail version, and the\nnumber goes up with every new release.\n\nWe keep the application list in\n[src\u002Ffirecfg\u002Ffirecfg.config](src\u002Ffirecfg\u002Ffirecfg.config)\n(\u002Fetc\u002Ffirejail\u002Ffirecfg.config when installed).\n\n## Security profiles\n\nMost Firejail command line options can be passed to the sandbox using profile\nfiles.\n\nYou can find the profiles for all supported applications in [etc\u002F](etc\u002F)\n(\u002Fetc\u002Ffirejail\u002F when installed).\n\nWe also keep a list of profile fixes for previous released versions in\n[etc-fixes\u002F](etc-fixes\u002F).\n\nIf you keep additional Firejail security profiles in a public repository,\nplease give us a link:\n\n* \u003Chttps:\u002F\u002Fgithub.com\u002Fchiraag-nataraj\u002Ffirejail-profiles>\n* \u003Chttps:\u002F\u002Fgithub.com\u002Ftriceratops1\u002Ffe>\n\nUse this issue to request new profiles:\n\n* [Profile requests](https:\u002F\u002Fgithub.com\u002Fnetblue30\u002Ffirejail\u002Fissues\u002F1139)\n\nYou can also use this tool to get a list of syscalls needed by a program:\n\n* [contrib\u002Fsyscalls.sh](contrib\u002Fsyscalls.sh)\n\n## Uninstalling\n\nfirecfg creates symlinks in \u002Fusr\u002Flocal\u002Fbin, so to fully remove firejail, run\nthe following before uninstalling:\n\n```sh\nsudo firecfg --clean\n```\n\nSee `man firecfg` for details.\n\nNote: Broken symlinks are ignored when searching for an executable in `$PATH`,\nso uninstalling without doing the above should not cause issues.\n\n## Latest released version: 0.9.80\n\n## Current development version: 0.9.81\n\n### Landlock support - ongoing\u002Fexperimental\n\n* Added on #6078, which is based on #5315 from ChrysoliteAzalea\u002Flandlock\n* Compile-time detection based on linux\u002Flandlock.h - if the header is found,\n  the feature is compiled in\n* Runtime detection based on whether Landlock is supported by the kernel and is\n  enabled on the system\n\n```text\nLANDLOCK\n       Landlock is a Linux security module first introduced in version 5.13 of\n       the  Linux  kernel.  It allows unprivileged processes to restrict their\n       access to the filesystem.  Once imposed, these restrictions  can  never\n       be  removed,  and  all child processes created by a Landlock-restricted\n       processes inherit these restrictions.  Firejail supports Landlock as an\n       additional  sandboxing  feature.  It can be used to ensure that a sand‐\n       boxed application can only access files and directories that it was ex‐\n       plicitly  allowed  to access.  Firejail supports populating the ruleset\n       with both a basic set of rules (see --landlock) and with a  custom  set\n       of rules.\n\n       Important notes:\n\n              - A process can install a Landlock ruleset only if it has either\n              CAP_SYS_ADMIN in its effective capability set, or  the  \"No  New\n              Privileges\"  restriction enabled.  Because of this, enabling the\n              Landlock feature will also cause Firejail to enable the \"No  New\n              Privileges\"  restriction,  regardless  of  the  profile  or  the\n              --nonewprivs command line option.\n\n              - Access to the \u002Fproc directory is managed through  the  --land‐\n              lock.proc command line option.\n\n              -  Access  to  the  \u002Fetc directory is automatically allowed.  To\n              override this, use the --writable-etc command line option.   You\n              can  also use the --private-etc option to restrict access to the\n              \u002Fetc directory.\n\n       To enable Landlock self-restriction on top of your current Firejail se‐\n       curity  features,  pass  --landlock flag to Firejail command line.  You\n       can also use --landlock.read, --landlock.write, --landlock.special  and\n       --landlock.execute  options  together with --landlock or instead of it.\n       Example:\n\n       $ firejail --landlock --landlock.read=\u002Fmedia --landlock.proc=ro \u002Fusr\u002Fbin\u002Fmc\n```\n\n### Profile Statistics\n\nA small tool to print profile statistics.  Compile and install as usual.  The\ntool is installed in the \u002Fusr\u002Flib\u002Ffirejail directory.\n\nRun it over the profiles in \u002Fetc\u002Fprofiles:\n\n```console\n$ \u002Fusr\u002Flib\u002Ffirejail\u002Fprofstats \u002Fetc\u002Ffirejail\u002F*.profile\nNo include .local found in \u002Fetc\u002Ffirejail\u002Fnoprofile.profile\nWarning: multiple caps in \u002Fetc\u002Ffirejail\u002Ftidal-hifi.profile\nWarning: multiple caps in \u002Fetc\u002Ffirejail\u002Ftqemu.profile\nWarning: multiple caps in \u002Fetc\u002Ffirejail\u002Ftransmission-daemon.profile\nWarning: multiple caps in \u002Fetc\u002Ffirejail\u002Ftrivalent.profile\n\nStats:\n    profiles\t\t\t1342\n    include local profile\t1341   (include profile-name.local)\n    include globals\t\t1307   (include globals.local)\n    blacklist ~\u002F.ssh\t\t1201   (include disable-common.inc)\n    seccomp\t\t\t1213\n    capabilities\t\t1335\n    noexec\t\t\t1214   (include disable-exec.inc)\n    noroot\t\t\t1105\n    memory-deny-write-execute\t320\n    restrict-namespaces\t\t1048\n    apparmor\t\t\t869\n    private-bin\t\t\t817\n    private-dev\t\t\t1172\n    private-etc\t\t\t842\n    private-cache\t\t865\n    private-lib\t\t\t86\n    private-tmp\t\t\t1036\n    whitelist home directory\t662\n    whitelist var\t\t975   (include whitelist-var-common.inc)\n    whitelist run\u002Fuser\t\t1305   (include whitelist-runuser-common.inc\n\t\t\t\t\tor blacklist ${RUNUSER})\n    whitelist usr\u002Fshare\t\t760   (include whitelist-usr-share-common.inc\n    net none\t\t\t452\n    dbus-user none \t\t766\n    dbus-user filter \t\t206\n    dbus-system none \t\t970\n    dbus-system filter \t\t13\n\n\n```\n","Firejail 是一个轻量级的安全工具，旨在通过为应用程序设置受限环境来保护 Linux 系统。它利用 Linux 命名空间、seccomp-bpf 和 Linux 能力等技术，使得进程及其后代拥有独立的全局共享内核资源视图，如网络栈、进程表和挂载表，从而降低安全漏洞风险。该项目几乎不依赖外部库，用 C 语言编写，支持在任何安装了 3.x 或更新版本内核的 Linux 计算机上运行。Firejail 可以用于沙盒化各种类型的服务或应用，包括服务器、图形界面程序乃至用户登录会话，并且针对一些常见的 Linux 应用程序（例如 Firefox、Chromium）提供了预设的沙盒配置文件。由于其直接基于 Linux 内核实现所有安全特性，因此具有较低的性能开销和简单的使用方式，非常适合需要增强安全性而又不想增加系统复杂性的场景。","2026-06-11 03:06:39","top_language"]