Package Details: opensnitch-git r379.2b49871-1

Git Clone URL: (read-only, click to copy)
Package Base: opensnitch-git
Description: A GNU/Linux port of the Little Snitch application firewall.
Upstream URL:
Licenses: GPL3
Conflicts: opensnitch
Provides: opensnitch
Submitter: None
Maintainer: lsf
Last Packager: lsf
Votes: 19
Popularity: 0.64
First Submitted: 2017-05-03 14:15
Last Updated: 2020-02-08 11:21

Latest Comments

1 2 3 4 5 6 ... Next › Last »

lsf commented on 2020-02-08 12:08

At that point it should pretty much just pull go dependencies, which always seems to hang for a moment without any output at that point, depending on your internet connection speed. Maybe changing dep ensure to dep ensure -v might get you more output on where it's stuck?

I just did a clean build of it and its AUR-dependencies in a clean chroot and everything seemed to build properly.

If you're using an AUR helper, you might want to give it a try without one or with another one (yay should work)?

tuqueque commented on 2020-02-08 01:50

Hi, I have a problem trying to install opensnitch-git... When it reaches the "Starting prepare()" message in the build process, it stays there forever and nothing happens. I know pretty much nothing about building from sources, but I know is not doing anything. No CPU usage, nothing:

==> Extracting sources...
  -> Creating working copy of opensnitch git repo...
Cloning into 'opensnitch'...
==> Starting prepare()...

squalou commented on 2020-01-06 11:07

Hi, still having issues with daemon start : write /sys/kernel/debug/tracing/kprobe_events: no such file or directory

For those having a working opensnitch : which kernel do you use ?

yochananmarqos commented on 2020-01-02 23:15

@lsf: Please see VCS, Go and Python package guidelines.

Proper working PKGBUILD.

squalou commented on 2019-08-08 11:54

Hi,my daemon doesn't start. In daemons logs I get this weird error.

[2019-08-08 11:51:14] !!! Error while enabling probe descriptor for opensnitch_exec_probe: write /sys/kernel/debug/tracing/kprobe_events: no such file or directory

Some issues in upstream projects seem to state I'm not alone ... did anyone face this ? I'm running 4.19 LTS kernel. In /proc/config.gz I can see : CONFIG_KPROBE_EVENTS=y

debugfs is correctly mounted, files do exist. (-rw-r--r-- 1 root root 0 8 août 13:51 /sys/kernel/debug/tracing/kprobe_events)

lsf commented on 2019-06-25 16:37

That shouldn't be necessary. python-unicode-slugify-git uses provides=(python-unicode-slugify). Your AUR helper should understand this (yay does).

eniac commented on 2019-06-25 15:09

python-unicode-slugify is unavailable, it should be replaced with python-unicode-slugify-git in the pkgbuild

lsf commented on 2019-04-24 21:25

No. Or rather: only under very specific circumstances. I don't know how much you know about gnupg/pgp, so I'll just keep it short: What you did is import a key of some person who signs packages with it. Now you can additionally verify the integrity of packages/files signed with this key (in addition to the basic checksums). In some cases, the keys used are provided by the maintainer of the software that is packaged, in other cases it's by the person packaging it for the AUR, providing different amounts of extra "trust". This would only be an issue if you'd now blindly trust everything signed with this key, installed AUR packages without inspecting them and the key owner intentionally created a "bad" package (or someone got hold of his key and created one). So basically: no, everything's fine, as long as you follow basic "AUR hygiene", as stated in: => "Warning: Carefully check the PKGBUILD, any .install files, and any other files in the package's git repository for malicious or dangerous commands. If in doubt, do not build the package, and seek advice on the forums or mailing list. Malicious code has been found in packages before."

washo commented on 2019-04-24 21:05

@lsf Thank's a lot! By the way, could this compromise the security of the system somehow?

lsf commented on 2019-04-24 18:56

You need to import the public key in your personal gpg keyring (there are ways around cluttering your regular keyring, but let's just stick with using it for simplicity). See:!

It boils down to gpg --recv-keys 8C004C2F93481F6B, but optimally you would also verify the fingerprint of the key as provided "upstream", to ensure it's the actual and correct key you've imported via the aforementioned command.