New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Consider adding SubGraph's "fw-daemon" tool #1757

Closed
bnvk opened this Issue Feb 18, 2016 · 7 comments

Comments

Projects
None yet
5 participants
@bnvk

bnvk commented Feb 18, 2016

The folks at SubGraph OS have made a really handy tool they call fw-daemon which monitors network requests and allows the user to allow / disallow specific requests. The daemon presents a focus grabbing widget that looks like:

subgraph-snitch

I think this is highly useful helping users better understand when certain applications are sending their data and where. SubGraph based their tool on LittleSnitch which is MacOS and I really miss on Linux. SubGraphs tool is not packaged yet, but we should look into the feasibility of integrating it with Qubes once it gets more refined. I assume making VM specific firewall rules will be a challenge if it is implemented differently!

@adrelanos

This comment has been minimized.

Show comment
Hide comment
@adrelanos

adrelanos Feb 18, 2016

Member
Member

adrelanos commented Feb 18, 2016

@bnvk

This comment has been minimized.

Show comment
Hide comment
@bnvk

bnvk Feb 18, 2016

@adrelanos not sure I understand what you're saying. This tool (like LittleSnitch) is really useful in letting a user know things like:

  • A non-Google application is phoning home to Google everytime you launch it
  • An application is suddenly making calls to a random URL

The former is just intrusive data mining / reporting that usually goes unnoticed. The later could be a sign of malware. Both of which are helpful to users.

bnvk commented Feb 18, 2016

@adrelanos not sure I understand what you're saying. This tool (like LittleSnitch) is really useful in letting a user know things like:

  • A non-Google application is phoning home to Google everytime you launch it
  • An application is suddenly making calls to a random URL

The former is just intrusive data mining / reporting that usually goes unnoticed. The later could be a sign of malware. Both of which are helpful to users.

@adrelanos

This comment has been minimized.

Show comment
Hide comment
@adrelanos

adrelanos Feb 21, 2016

Member

The output of such tools is not reliable as in not to be trusted.
Effective containment of malicious applications on that level is in
vain. Otherwise we would not require Qubes. If applications are
untrusted, the right thing to do is to not install them. Such tools can
lead to a false sense of security which these are incapable to provide.

lightbeam (firefox add-on) and perhaps noscript are better suited to
educate users about data mining. [however I am not arguing for
pre-installing them]

Brennan Novak:

  • A non-Google application is phoning home to Google everytime you
    launch it

I think it's up to us distribution maintainers not to pre-install such
applications. And to make sure these do not even enter upstream
repositories. And to complain loudly should this ever happen.

Such as people loudly complained about the Ubuntu search box amazon data
leak (see EFF blog post). Except for that case, I don't think we yet
have phoning home software in Libre Software repositories yet.

  • An application is suddenly making calls to a random URL
    [...] could be a sign of malware. Both of which are helpful to users.

As soon as such tools get pre-installed by default on a considerable
amount of systems, malware would take precautions to prevent getting
spotted by tools such as fw-daemon. Tunnel their illicit communications
by example through DNS.

Member

adrelanos commented Feb 21, 2016

The output of such tools is not reliable as in not to be trusted.
Effective containment of malicious applications on that level is in
vain. Otherwise we would not require Qubes. If applications are
untrusted, the right thing to do is to not install them. Such tools can
lead to a false sense of security which these are incapable to provide.

lightbeam (firefox add-on) and perhaps noscript are better suited to
educate users about data mining. [however I am not arguing for
pre-installing them]

Brennan Novak:

  • A non-Google application is phoning home to Google everytime you
    launch it

I think it's up to us distribution maintainers not to pre-install such
applications. And to make sure these do not even enter upstream
repositories. And to complain loudly should this ever happen.

Such as people loudly complained about the Ubuntu search box amazon data
leak (see EFF blog post). Except for that case, I don't think we yet
have phoning home software in Libre Software repositories yet.

  • An application is suddenly making calls to a random URL
    [...] could be a sign of malware. Both of which are helpful to users.

As soon as such tools get pre-installed by default on a considerable
amount of systems, malware would take precautions to prevent getting
spotted by tools such as fw-daemon. Tunnel their illicit communications
by example through DNS.

@marmarek

This comment has been minimized.

Show comment
Hide comment
@marmarek

marmarek Feb 22, 2016

Member

Such tool can be useful for training your firewall. To setup firewall for particular VM to access only resources you want.

For example:
You have banking VM with web browser used only to access your online banking. Now you want to allow it to access only yourbank.com site (over HTTPS only of course). But after you setup such firewall, you notice that some images on the page do not show. Now such fw-daemon would be useful to find out that you need to add also static.yourbank.com too (but not google-analytics.com).

Member

marmarek commented Feb 22, 2016

Such tool can be useful for training your firewall. To setup firewall for particular VM to access only resources you want.

For example:
You have banking VM with web browser used only to access your online banking. Now you want to allow it to access only yourbank.com site (over HTTPS only of course). But after you setup such firewall, you notice that some images on the page do not show. Now such fw-daemon would be useful to find out that you need to add also static.yourbank.com too (but not google-analytics.com).

@bnvk

This comment has been minimized.

Show comment
Hide comment
@bnvk

bnvk Feb 23, 2016

I think it's up to us distribution maintainers not to pre-install such
applications

@adrelanos because users never install software on their own? And they don't all know how to use Wireshark or netstat? I ran Atom Editor by Github for months (on my Qubes) machine, before I used it again on my Mac and LittleSnitch informed me there was a "debugging" module enabled by default that submitted to google-analytics.com everytime I used the app... 😦

We might want to enable fw-daemon by default except for advanced users, but I think it should definitely be included and integratable with Qubes VM firewalls!

bnvk commented Feb 23, 2016

I think it's up to us distribution maintainers not to pre-install such
applications

@adrelanos because users never install software on their own? And they don't all know how to use Wireshark or netstat? I ran Atom Editor by Github for months (on my Qubes) machine, before I used it again on my Mac and LittleSnitch informed me there was a "debugging" module enabled by default that submitted to google-analytics.com everytime I used the app... 😦

We might want to enable fw-daemon by default except for advanced users, but I think it should definitely be included and integratable with Qubes VM firewalls!

@ag4ve

This comment has been minimized.

Show comment
Hide comment
@ag4ve

ag4ve Feb 23, 2016

ag4ve commented Feb 23, 2016

@andrewdavidwong

This comment has been minimized.

Show comment
Hide comment
@andrewdavidwong

andrewdavidwong Oct 20, 2016

Member

Closing as retroactive duplicate of #2350, per #2350 (comment).

Member

andrewdavidwong commented Oct 20, 2016

Closing as retroactive duplicate of #2350, per #2350 (comment).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment