Too many Firefox notifications about picosnitch HOT 4 CLOSED

I'm also curious about this - I get many messages from firefox and from thunderbird and not sure how to ignore them:

2022-01-15 18:20:16 DNS Res~er #206 - /usr/lib/firefox/firefox (name)
2022-01-15 18:20:16 DNS Res~er #207 - /usr/lib/firefox/firefox (exe)
2022-01-15 18:20:16 DNS Res~er #207 - /usr/lib/firefox/firefox (name)
2022-01-15 18:26:49 DNS Res~er #882 - /opt/thunderbird/thunderbird-bin (name)
2022-01-15 18:26:49 DNS Res~er #883 - /opt/thunderbird/thunderbird-bin (name)
2022-01-15 18:26:49 DNS Res~er #884 - /opt/thunderbird/thunderbird-bin (name)

from picosnitch.

I updated it so now you should only get notifications on new executables or hashes, not process names (these will still appear in the log file though). I also tidied up the messages a bit. aa1f698

from picosnitch.

Well, the log file is what I monitor. I think it'll help to remove meaningless lines from the log file too.

from picosnitch.

In that case I wouldn't say it's meaningless, because other than just including the first seen name, there isn't really a best way to determine which name to include.

Also in cases for things like containers, the executable path is basically useless, and you can have multiple different executables appear to have the same path, usually they'd also have the same name, but not always, so it could be useful to have some differentiation other than the hash since that could be delayed, or fail if the process was extremely short lived.

Also in your example it won't be as bad (no more duplicates)

2022-01-12 16:11:42 DNS Resolver #3 - /snap/firefox/838/usr/lib/firefox/firefox (new name, exe)
2022-01-12 16:11:43 DNS Resolver #4 - /snap/firefox/838/usr/lib/firefox/firefox (new name, exe)
2022-01-12 16:11:44 DNS Resolver #8 - /snap/firefox/838/usr/lib/firefox/firefox (new name, exe)
...

from picosnitch.