[Bug] Signed executables labeled "Not signed" in the Network alert popup on initial network access

[dlong500]

Checklist

• I have used the search function to see if someone else has already submitted the same bug report.
• I will describe the problem with as much detail as possible.

App version

3.8.3

Windows version

Windows 10 22H2

Steps to reproduce

1. Open a signed app that attempts network access for the first time
2. Wait for the network alert popup and examine the "Signature" label
3. Hover over the name of the executable to display file and signature details

Expected behavior

Simplewall should always show the signature name for a signed executable in the Network alert popup signature field.

Actual behavior

Simplewall frequently (if not always) shows "Not signed" in the Network alert popup for the very first time an executable attempts network access. If the alert is dismissed (not blocked), the next time it displays for that same executable the correct signature info is shown. See the screenshots for:

1. The initial popup
2. The initial popup w/ hover over the executable name
3. The subsequent popup after the initial one is dismissed

Note that this is just an example and it is happening with any executable (including Microsoft signed exes).

Logs

No response

[henrypp]

i think it fixed, check it here

simplewall.zip

[dlong500]

I've only been able to test it on a few executables so far but it seems to have resolved the issue. Thanks!

I'd need to start over from scratch to do a more thorough test (as so many of the executables already have rules and/or have already displayed the initial popup), but I'm pretty sure we're good now.

[dlong500]

Well shoot, I just had another couple alerts pop up from Adobe-related signed executables exhibiting the same symptom. It seems better than before (not as many initial popups showing unsigned), but the issue still seems to be present.

[henrypp]

ok, i see, checked and now it fixed, wait for tomorrow!