Full access might be a bit too encompassing ?

[whismerhill]

I suggest "Full access Outbound only" additional quick rule ? or just shortened to "Outbound access" or "Outbound full" e.g. a browser probably doesn't need an inbound access and so on...

Thanks.

[Mrnofish]

I would very much love to have a couple of "allow specific" buttons that use data from the request itself to pre-fill the dialog.

"Allow Specific Proto" would automatically configure the rule for e.g. TCP or UDP Outbound when the app is requesting either a TCP or UDP Outbound connection.

"Allow Proto/IPs" would automatically configure the rule for e.g. TCP Outbound, restricted to the IP addresses the application is trying to connect to.

This would save a lot of time.

[whismerhill]

So I have been using "custom" for everything now it works....

but it's kinda slow

two suggestions : -adding a few more profiles to cater to the most common needs -alternatively adding the ability to add our own custom generic profiles that can be applied quickly would be awesome

[DavidXanatos]

i like he odea of cutom profiles, but still i could preset them with the most commen use cases.

would you want to suggest some? so outbound only inbound only what else?

[whismerhill]

well outbound only is pretty much the one I need and can think about @Mrnofish was suggesting TCP outbound & UDP outbound if I'm not mistaken on his post no idea if he meant combined or individual

for my usage (games & occasional game servers self hosted) I guess an inbound TCP & UDP restriction could make sense... I'm security aware but by far not a security expert either ...

[deflock]

If LAN only does not include all local/private subnets it would be nice to have this one

[DavidXanatos]

The next build will have options InBound Access Only and OutBound Access Only

I don't think its often required to restrict things to TCP or UDP only, so no quick button for that.

But if you want to, you can already now double click on any Connection Attempt entry in the notification PopUp and you will be presented with a rule dialog that is pre filled with the details of that log entry, Protocol, IP, Port, you only need to pick the action and press ok.

[DavidXanatos]

build 0.83 is out, try it out

[whismerhill]

seems good, couldn't test much.

[whismerhill]

ok so I tried it out more thorougly

it seems "outbound access" rule causes a "problem" of sorts it does 1 rule that allows outbound traffic right ? and since it doesn't add another rule that block inbound traffic then it means you might get a popup to ask again about the inbound traffic this time which isn't a problem by itself but it means a new custom rule to block inbound traffic

otherwise seems great. 👍