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
How would I sign the installer myself? If I run the installer on my windows machine it gives me warnings like that:
It says "The computer was protected by Windows. Microsoft Defender SmartScreen prevented an unknown app from starting. Running this app may pose a risk to the PC." If you click on "Weitere Informationen" it shows the publisher "Web Lite Solutions Corp"
So I think this is because the app gets changed after it has been signed (so from then on it's unknown) - I guess I have read that there is a URL payload added after signing it?
My users won't be happy with the app publisher "Web Lite Solutions Corp" ... (no offence of course :-) so signing it myself might be a solution for both problems.
Best regards
Jörg
The text was updated successfully, but these errors were encountered:
There is nothing modified after it was signed. If it were modified, either it would refuse to open it, or it would show "Unknown publisher".
This is a standard Windows defender message, and it is unavoidable for smaller apps. I may add support for signing using your own certificate in the future, but the only difference it would make is that it would show a different publisher name in this dialog.
How would I sign the installer myself? If I run the installer on my windows machine it gives me warnings like that:
It says "The computer was protected by Windows. Microsoft Defender SmartScreen prevented an unknown app from starting. Running this app may pose a risk to the PC." If you click on "Weitere Informationen" it shows the publisher "Web Lite Solutions Corp"
So I think this is because the app gets changed after it has been signed (so from then on it's unknown) - I guess I have read that there is a URL payload added after signing it?
My users won't be happy with the app publisher "Web Lite Solutions Corp" ... (no offence of course :-) so signing it myself might be a solution for both problems.
Best regards
Jörg
The text was updated successfully, but these errors were encountered: