Sysdig
firejail
Sysdig | firejail | |
---|---|---|
10 | 139 | |
7,608 | 5,476 | |
0.8% | - | |
8.5 | 9.7 | |
6 days ago | 7 days ago | |
C++ | C | |
GNU General Public License v3.0 or later | GNU General Public License v3.0 only |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Sysdig
-
Introducing Flora: Newly launched eBPF observability solution with near-zero resource overhead, for optimal performance in modern cloud-native environments
Also, have you already looked at sysdig? I don't think they're exactly tracing focused, but they've been around a long time and the times I've tried it locally it's been neat
-
Problem building the scap kernel module for sysdig
Seems like sysdig has some problems with newever kernels [1]. Also, the version in the repos should probably be updated (xbps: 28.0, upstream: 30.0). Maybe updating it would even solve the issue.
- How to automate container syscall profiling
-
Sysdig VS ThreatMapper - a user suggested alternative
2 projects | 11 Apr 2022
-
Systemd service sandboxing and security hardening 101
FWIU, e.g. sysdig is justified atop whichever MAC system.
In the SELinux MAC system on RHEL and Debian, in /etc/config/selinux, you have SELINUXTYPE=minimal|targeted|mls. RHEL (CentOS and Rocky Linux) and Fedora have SELINUXTYPE=targeted out-of-the-box. The compiled rulesets in /etc/selinux/targeted are generated when
With e.g gnome-system-monitor on a machine with SELINUX=permissive|enforcing, you can right-click the column header in the process table to also display the 'Security context' column that's also visible with e.g. `ps -Z`. The stopdisablingselinux video is a good SELinux tutorial.
I'm out of date on Debian/Ubuntu's policy set, which could also probably almost just be sed'ed from the current RHEL policy set.
> * SELinux is deny by default, while in systemd you're playing whack-a-mole anyway, and are expected to add directives one by one until the application stops working. Unit logs usually make it obvious if something was denied.*
DENY if not unconfined is actually the out-of-the-box `targeted` config on RHEL and Fedora. For example, Firefox and Chrome currently run as unconfined processes. While decent browsers do do their own process sandboxing, SELinux and/or AppArmor and/or 'containers' with a shared X socket file (and drop-privs and setcap and cgroups and namespaces fwtw) are advisable atop really any process sandboxing?
Given that the task is to generate a hull of rules that allow for the observed computational workload to complete with least-privileges, if you enable like every rule and log every process hitting every rung on the way down while running integration tests that approximate the workload, you should end up with enough rule violations in the log to even dumbly generate a rule/policy set without the application developer's expertise around to advise on potential access violations to allow.
From https://github.com/draios/sysdig :
> "Sysdig instruments your physical and virtual machines at the OS level by installing into the Linux kernel and capturing system calls and other OS events. Sysdig also makes it possible to create trace files for system activity, similarly to what you can do for networks with tools like tcpdump and Wireshark.
Probably also worth mentioning: "[BETA] Auditing Sysdig Platform Activities"
-
Does anyone here use sysdig? What are your thoughts?
I'm about to go on an interview with them I am curious if anyone here uses sysdig on an enterprise level and what your thoughts are on their product? It's totally open source and looks awesome from what I can tell so far.
-
Arch and Debian
This https://github.com/draios/sysdig/wiki/How-to-Install-Sysdig-for-Linux
-
Ask HN: What’s your favorite free, self-hosted monitoring dashboard?
DO offers metrics directly from the Dash, just sayin.
Also, https://github.com/draios/sysdig
-
2020, the year of unexpectedness
fix(driver/bpf): exact check on bpf_probe_read_str() return value #1612
firejail
-
Sandboxing All the Things with Flatpak and BubbleBox
bubblewrap is designed as a low-level too. There is nothing quick and dirty about it. It disallows everything by default and you have to be explicit about what you want to share with the host. If your application needs complex permissions/resources, then you will need to have a complex bubblewrap command line.
Once you have figured out which permissions/resources you need for a given program, you can wrap the command line invocation in a shell script.
If you want other people to do the work of defining permissions/resources, then have a look at firejail: https://github.com/netblue30/firejail
-
Ask HN: What are some unpopular technologies you wish people knew more about?
Firejail is cool: https://github.com/netblue30/firejail
Linux namespaces/cgroups but nowhere near as heavy as Docker.
I use it when I want to limit the memory of a Python script:
```
-
Toolship: A (More) Secure Workstation
Firejail can also be a useful option, though no good if you're on Mac https://firejail.wordpress.com/
Uses the same Linux primitives as docker etc, but can be a bit more ergonomic for this use case
-
Firejail: Light, featureful and zero-dependency security sandbox for Linux
Firejail, Flatpak (which uses Bubblewrap under the hood), and Snap (which uses AppArmor) all use the same underlying technology: Linux namespaces.
This question comes up a lot, and has been answered here: https://github.com/netblue30/firejail/wiki/Frequently-Asked-...
TL;DR: Firejail has much more comprehensive features than Flatpak (Bubblewrap). Firejail also has more comprehensive network support, support for AppArmor and SELinux, and easier seccomp filtering.
Compared to Snap (which uses AppArmor), Firejail is compatible with AppArmor and again goes above and beyond with a lot of additional features.
-
Bubblewrap – Low-level unprivileged sandboxing tool used by Flatpak
Wonderful little tool, too bad you must chain various exec calling tools to get cgroups (a bit akin to `ionice ... nice ... cmd`) and Linux users namespaces can't allow UNIX sockets while preventing network access (I think?).
Migrated from Firejail when its complexity annoyed me too much and I hit https://github.com/netblue30/firejail/issues/3001 (Firejail doesn't like parens or brackets in --put/--get parameters) to a badly NIH version using bwrap and bash to have "profiles":
- Firejail: Light featureful and zero-dependency security sandbox for Linux
-
Do, or do not. There is no try
Firejail does this. The profile database is the two "profile" directories in https://github.com/netblue30/firejail/tree/master/etc
-
Strange times make for strange friends...
What do you mean by a Firefox container? Do you mean FireJail?
What are some alternatives?
Wireshark - Read-only mirror of Wireshark's Git repository at https://gitlab.com/wireshark/wireshark. ⚠️ GitHub won't let us disable pull requests. ⚠️ THEY WILL BE IGNORED HERE ⚠️ Upload them at GitLab instead.
bubblewrap - Low-level unprivileged sandboxing tool used by Flatpak and similar projects
perf-tools - Performance analysis tools based on Linux perf_events (aka perf) and ftrace
flatpak - Linux application sandboxing and distribution framework
httpstat - curl statistics made simple
bubblejail - Bubblewrap based sandboxing for desktop applications
mitmproxy - An interactive TLS-capable intercepting HTTP proxy for penetration testers and software developers.
Flatseal - Manage Flatpak permissions
mtr - Official repository for mtr, a network diagnostic tool
yabai - A tiling window manager for macOS based on binary space partitioning
Dripcap
podman - Podman: A tool for managing OCI containers and pods.