summaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
authorkali <kali@win>2020-10-27 23:38:13 +0100
committerkali kaneko (leap communications) <kali@leap.se>2020-11-04 12:33:29 +0100
commit3dc345bc2b9f600974df6acce84ab671ab8c8e5d (patch)
treed7b050c0acb26a8cfb5678dfd7f3131767440963 /docs
parentbfd3419b4fafaad1f9f87bda0810fe4f7c73578b (diff)
[pkg] sign windows binaries
- Resolves: #383
Diffstat (limited to 'docs')
-rw-r--r--docs/build.windows.rst33
1 files changed, 33 insertions, 0 deletions
diff --git a/docs/build.windows.rst b/docs/build.windows.rst
index 27edcbc..8743126 100644
--- a/docs/build.windows.rst
+++ b/docs/build.windows.rst
@@ -15,3 +15,36 @@ Assuming you have the vendor path in place and correctly configured, all you nee
export PATH="/c/Qt/Qt5/bin/":"/c/Qt/QtIFW-3.2.2/bin":$PATH
export VENDOR_PATH=providers
make vendor && make installer
+
+
+checking signatures
+-------------------
+we should be signing all binaries on a release build.
+
+to check the binaries have proper signatures, you can use the sigcheck
+utilities, part of the sysinternals suite:
+
+https://docs.microsoft.com/en-us/sysinternals/downloads/sysinternals-suite
+
+unzip and place sigcheck.exe somewhere in your path.
+
+make sure to pass -accepteula parameter on some manual run so that it does not
+ask again.
+
+adding metadata to binaries
+---------------------------
+TODO: add metadata properly
+https://github.com/electron/rcedit/releases/tag/v1.1.1
+https://stackoverflow.com/questions/284258/how-do-i-set-the-version-information-for-an-existing-exe-dll
+
+the steps to do release signatures are::
+
+ make build
+ make dosign
+ make installer
+ make sign_installer
+
+
+unreviewed notes
+----------------
+see comment about patching dlls and windeployqt not being needed anymore https://stackoverflow.com/a/61910592