-
Notifications
You must be signed in to change notification settings - Fork 1k
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
Is the firewall prompt on every update still an issue? #1816
Comments
Firewall prompts (and many other problems) are still present in Squirrel.Windows due to the app exe moving between versions. Windows was not designed for apps to run this way. In Clowd.Squirrel, a fork, this has been solved by having the app run from a I see you're also using electron, and there has been some effort to build a Clowd.Squirrel electron forge maker which supports the fork so electron users can also switch over easily. Although I wouldn't say it's ready to use yet, within a couple of months v3 and the maker should be ready for production apps. |
Thanks for the help, maker-clowd.squirrel looks interesting, I'll give a try soon as my options are running out. For anybody else reading, pre-allowing the root directory in firewall is not an option. I'll just try enabling the used ports next |
Ok, I just found out that I can disallow access or neglect the prompt, it makes no difference to my app, all network functions as usual, autoUpdate works well too, if I could just not trigger the prompt, that'd be great for me |
@rzfzr If you don't want to trigger the prompt, only open the socket on |
@anaisbetts Is this configurable? If so, where? I'm using |
@fredluetkemeier I believe she means whenever you do open a socket or your app code, if you don't then you shouldn't get the prompt(?) |
Squirrel version(s)
"electron-builder-squirrel-windows": "^23.1.0",
"electron-squirrel-startup": "^1.0.0",
Description
I switched to squirrel in order to use electron's autoUpdater, however the firewall exception prompt at every single update is an issue.
Reading this (#1045) gives me the impression that it should be solved...
The security alert is for the \local\app\app-0.0.0.X\app.exe , not for the \local\app\app.exe, as you can see in the image:
Application signing would solve this? Or is #951 our best solution at the moment?
It would being able to trust either the author or the root directory.
Related: #951, #868, #1052, #798
The text was updated successfully, but these errors were encountered: