This commit is contained in:
@@ -252,3 +252,28 @@ DOCKER / LINUX CHEAT SHEET
|
||||
sudo docker exec -it xfer_ayanova_1 ash
|
||||
|
||||
AYANOVA files are stored in droplet outside docker in /var/lib/ayanova
|
||||
|
||||
|
||||
########################################################################################
|
||||
Windows installer worksheet
|
||||
|
||||
INNOSETUP still the way to go apparently
|
||||
|
||||
|
||||
SIGNING
|
||||
Short story, probably not worth the hassle, needs to come from an authority, expires every year, basically bullshit
|
||||
But if it becomes necessary then:
|
||||
|
||||
Can sign the setup to avoid issues:
|
||||
Authenticode is what we want
|
||||
https://docs.microsoft.com/en-us/visualstudio/deployment/clickonce-and-authenticode?view=vs-2019
|
||||
|
||||
This guy had to do it and has advice:
|
||||
https://mkaz.blog/code/code-signing-a-windows-application/
|
||||
|
||||
This is how to find the sign tool to sign things:
|
||||
where /R c:\ makecert.*
|
||||
https://stackoverflow.com/questions/51418366/makecert-exe-missing-in-windows-10-how-to-get-it-and-use-it
|
||||
|
||||
Useful looking:
|
||||
https://blog.jayway.com/2014/09/03/creating-self-signed-certificates-with-makecert-exe-for-development/
|
||||
Reference in New Issue
Block a user