fw-daemon
fw-daemon copied to clipboard
subgraph
Subgraph Application Firewall
i get this error: > gbp:error: 'git-pbuilder -us -uc' failed: it exited with 1 when i run > #gbp buildpackage -us -uc
Hi, since you're solely relying on the `/proc` filesystem in order to correlate connections to pids and pids to application paths, your software is vulnerable to path manipulation. Long story...
e.g. we plan to built default rules, one easy example is ricochet. Something like: [ricochet|/usr/bin-oz/ricochet] ALLOW|*.onion:*|SYSTEM|-1:-1| These would be included in a Subgraph package and would allow us to issue...
See https://github.com/subgraph/go-nfnetlink/issues/5
Fixes build failing without manual intervention due to `mono-sgen` running as a dependency and failing due to missing PAX flags Requires https://github.com/subgraph/subgraph-debian-packages/pull/5
As Subgraph Firewall's complexity and scope grows, we more than ever need automated tests for FW policy evaluation and traffic source identification. This will help us clearly define & articulate...
For example, enabling redacted logs: In /etc/sgfw/sgfw.conf LogRedact = true Also the SOCKS5 proxy port config.
Gnome shell. Can't reliably reproduce. More on this later as it is release-blocking bug.
While this is currently underway as an extension to the new built-in fw-daemon SOCKS5 server, an even better way would be to use passive inspection via netfilter queues to be...
Not believed to be due to natural causes: Oct 1 01:48:35 subgraph fw-daemon[4098]: Client read error: EOF Oct 1 01:48:35 subgraph fw-daemon[4098]: ERRO 1f0 TLSGuard violation: Dropping traffic from /usr/lib/chromium/chromium...