Skip to content

Wildcard for allowed application names. #853

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

Closed
acos21 opened this issue Feb 5, 2021 · 3 comments
Closed

Wildcard for allowed application names. #853

acos21 opened this issue Feb 5, 2021 · 3 comments

Comments

@acos21
Copy link

acos21 commented Feb 5, 2021

I have several applications running that require a frequent update.

The files that contain the update all have a somewhat different filename (dropbox is one of them).

This results in me having to authenticate new files multiple times a day on different machines.

2021-02-06 00_09_14-simplewall

Any way i can allow "dropboxclient*" files to always be Allowed?

@captainhook
Copy link

captainhook commented Feb 7, 2021

@henrypp has covered this in #463
It's a pain so for now I'm just temporarily disabling simplewalll to update/run software that does this.

Also see #494, "No, wildcard will not be implemented, ever!"
And #136, "No wildcards will be in simplewall, ever."

@Chaython
Copy link

He's stubborn about implementing new things, but it's good to not make it a bloated mess.

You could fork and implement yourself, or create a batch file or something to write new rules to your profile xml, or to launch an app with loopback etc.

@skupjoe
Copy link

skupjoe commented Oct 1, 2023

Is anybody aware of a fork or PR that implements this feature?

Repository owner locked as off-topic and limited conversation to collaborators Oct 1, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

5 participants