Cannot wildcard match directories / not working

[Rubber-Duckie]

What happened:

Various applications can spawn executables that need internet access. These executables can be created in sub directories which are generated with a random name.

Take for example visual studio, rather notorious for this, where it uses the temporary directory in which it will create subdirectories with random names, a new name every time it runs.

i.e. C:\Users\User1\AppData\Local\Temp\uogzuxa0.jm3\resources\app\ServiceHub\Services\Microsoft.VisualStudio.Setup.Service

This happens every few hours thus the Portmaster creates a new profile for each unique path it sees, forever. This effectively destroys the ability for the application to be of any use.

Despite having edited the profile for the executable, and having inserted a wildcard into the path within the edit profile option, it does not function as expected.

see the screen shot below.

What did you expect to happen?:

Edit the profile, insert a asterisk for 'match any string' within the file path. From then on, the file path matching logic will use that single profile for the matching instances detected.

i.e. C:\Users\User1\AppData\Local\Temp\*\resources\app\ServiceHub\Services\Microsoft.VisualStudio.Setup.Service

[github-actions[bot]]

Greetings and welcome to our community! As this is the first issue you opened here, we wanted to share some useful infos with you:

• 🗣️ Our community on Discord is super helpful and active. We also have an AI-enabled support bot that knows Portmaster well and can give you immediate help.
• 📖 The Wiki answers all common questions and has many important details. If you can't find an answer there, let us know, so we can add anything that's missing.

[Rubber-Duckie]

• I notice there is a regular expression capability.

• I have merged all the duplicates into a single master.

• I have created a regex to attempt to undertake the same match.

  

• Will update here if this works for reference for other people with similar expectations.

• I am anticipating this will be marked expected behavour since you have NOT implemented wildcard matching strings in the fingerprint feature, and regex is the only way...

[Rubber-Duckie]

Confirm Regex provides the expected behavour. Might be worth adding notes to the exclamation if the intent is for path matching not to support any string wildcards