search

objective-see / LuLu

LuLu is the free macOS firewall
GNU General Public License v3.0
9.97k stars 464 forks source link

Allow multiple rules per process #10

Open leipert opened 7 years ago

leipert commented 7 years ago

I really would like more granular level of control over which IPs a process connects to. I definitely do not want a process to connect to any Tracking system, e.g. Google, while maintaining connections to the APIs of the process.

gondo commented 6 years ago

currently the rules are per process. it would be much more helpful if they were per process + destination (different rule for different port)

KizzyCode commented 6 years ago

Yeah, something like Default Block *:* + Allow IP:Port per process/application would be nice. This would allow you, for example, to limit your e-mail program to your mail-servers to block all "efail" attacks and tracking-attempts etc.

ctramnitz commented 6 years ago

Yeah, per port and/or per destination network rules would make a lot of sense.

Wdavery commented 6 years ago

Another vote for this. This feature is huge.

tbnv commented 6 years ago

Voting for this as well, since it's kind of a deal breaker. Mostly for the same reason as @leipert: blocking access to Analytics or Crashlytics should not prevent the process from talking to other APIs.

peterloron commented 6 years ago

I came here just for this reason. LuLu is good so far, but adding this feature would really make it awesome.

grzegor commented 6 years ago

This would be awesome!

inteist commented 6 years ago

This would be an awesome addition! Hope someone who is more networking savvy than myself would have the time to do a PR.

bretello commented 5 years ago

+1

working-name commented 5 years ago

+1

sashsvamir commented 5 years ago

waiting this feature too!

nax-bedroom commented 5 years ago

It would be super cool to control which applications have access to specific addresses.

360fun commented 5 years ago

👍 🌳

luco commented 5 years ago

Please add this!

ghost commented 5 years ago

+1 , this feature is a must for any firewall :)

OiCkilL commented 5 years ago

Can't wait!

aAmahQpwRk commented 4 years ago

+1, it's the only feature that keeps me from using LuLu as my main firewall!

matatablack commented 4 years ago

+1, it's the only feature that keeps me from using LuLu as my main firewall!

What are you using as main firewall? I was very happy with LuLu but now i have an use case that need this feature, i need to use another firewall! :( :( :( :(

smachi commented 4 years ago

+1

PencilNotPen commented 4 years ago

+1

pmjohann commented 4 years ago

+1

jawsoftware commented 4 years ago

+1

LuckyLukert commented 4 years ago

I'm wondering what's the status on this. Do you plan on implementing this in near future?

360fun commented 4 years ago

in the meanwhile I decided to try another firewall... :( I really hope that this feature will come in the future to switch back.

ghost commented 4 years ago

This is a really important request and I now have a use case: It's a VNC client that I want to green-light for LAN connections but not on the Internet, where it could cross unwanted boundaries and 'phone home' where it has no business doing so.

I'm sad LuLu has not added this, despite 3 years of strong community request for it.

anymos commented 4 years ago

do not get it, why after 3 years it is still not implemented, this is a basic need. Going to find another firewall then ..

objective-see commented 4 years ago

Aloha, I just pushed LuLu 2.0.0 (beta!) Amongst other things, supports multiple rules per process (finally!)

Per Process Rules

(notarized) Download: https://bitbucket.org/objective-see/deploy/downloads/LuLu_2.0.0_BETA.zip

Would love any beta-testers/feedback! Bugs? → https://github.com/objective-see/LuLu/issues

p.s. To view (log) output, while test, run the following from the Terminal: log stream --level debug --predicate="subsystem='com.objective-see.lulu'"

360fun commented 4 years ago

This is just awesome: thank you!!! 🥳

supervisitor commented 4 years ago

Aloha, I just pushed LuLu 2.0.0 (beta!)

sounds and looks good!

however, i would prefer radio-buttons instead of the drop-down-menu. is faster and easier to use. and it has the place on the window. even if you would offer a complete list of all possibilities, meaning something like this::

are there any more useful options? i think this corresponds to the most important wishes of all... ok, a slider for the cidr or a drop-down-menu... 😇 LuLu-radiorules

the more granular rule-set like this is on my wish list... thanks a lot for rethinking

initrd commented 3 years ago

+1 for allowing more options for rules. Ex: I would like to whitelist all of [Zoom's](https://support.zoom.us/hc/en-us/articles/201362683-Network-Firewall-or-Proxy-Server-Settings-for-Zoom IP addresses] to the specific process. The current options are very granular - either allow every IP Zoom connects to, or whitelist /80, /443 - neither of which are ideal.

D-e-n-t commented 3 years ago

+1 for Network Options. On the popup, the options can/should be limited - too many options in the image above. If users/admins need to refine the rules, they should be able to do that in the rules window of the app. The dialog should be limited to 2-3 options at most, because it is intrusive.

There should be an option to deploy rules to hosts. I.e. have the extension periodically check for a "new-rules.plist" file deployed by administrators. Alternatively, the new-rules file could be pulled remotely like the block list. I would like to see a preference to allow the existing rules to be overwritten by the deployed or remote ruleset, or merged into the existing rules.

It would be nice to allow for the new rules to be signed in some way - with the public key saved in the preference file so that only trusted rules would be loaded automatically.

mandeepsinghgill commented 1 year ago

I turned on Passive mode in LuLu firewall settings and it works fine for me.

inspiredearth commented 3 months ago

Aloha, I just pushed LuLu 2.0.0 (beta!) Amongst other things, supports multiple rules per process (finally!)

p.s. To view (log) output, while test, run the following from the Terminal: log stream --level debug --predicate="subsystem='com.objective-see.lulu'"

Would you please elaborate on rule prioritisation, now that there are Process and Endpoint level rules?

For example, if I've blocked 10 endpoints for an application, and then I Allow the Process, to the prior Blocks get applied before the Allow (Process) rule is applied? If not, then all the other rules are made ineffective if a Process rule is added, so I am assuming there is rule prioritisation taking place, but would like to know for certain.

Thank you.