You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There are certain types of apps which will "spawn" installers, i.e. download them from the internet and execute those downloaded installers. The challenge here is that neither rules for the original app work nor do temporary rules for the child apps work. If the child app, say "setup.exe" cannot connect to the internet, the install process immediately fails. However, the spawned app remains in a temporary folder and the next time the original app tries to update itself it will download and execute "setup (1).exe". Like this, the update process will never succeed and I cannot fathom how to make internet access work in a semi-automated way. Up until now, I have disabled simplewall for those kinds of installers and after a successful update have re-enabled it.
Is there something you would recommend in this situation?
Maybe if the child process could be made to wait as long as simplewall displays a prompt it could work?
Or maybe simplewall could also monitor and include child processes?
The text was updated successfully, but these errors were encountered:
There are certain types of apps which will "spawn" installers, i.e. download them from the internet and execute those downloaded installers. The challenge here is that neither rules for the original app work nor do temporary rules for the child apps work. If the child app, say "setup.exe" cannot connect to the internet, the install process immediately fails. However, the spawned app remains in a temporary folder and the next time the original app tries to update itself it will download and execute "setup (1).exe". Like this, the update process will never succeed and I cannot fathom how to make internet access work in a semi-automated way. Up until now, I have disabled simplewall for those kinds of installers and after a successful update have re-enabled it.
Is there something you would recommend in this situation?
Maybe if the child process could be made to wait as long as simplewall displays a prompt it could work?
Or maybe simplewall could also monitor and include child processes?
The text was updated successfully, but these errors were encountered: