outline-server/third_party/jsign
J. Yi 9531932be9
build(manager/electron): 👷 add option to use GCP KMS for signing (#1168)
In this changeset:

- upgraded `jsign.jar` to version `4.2`
- add an option to leverage `gcp-hsm` certificate to sign Windows executables
- please note that [GCP does not support SHA-1](https://cloud.google.com/kms/docs/algorithms#asymmetric_signing_algorithms), and here are the consequences of not adding SHA-1 to the binary signatures:
   1. [SHA-1 is deprecated by Microsoft](https://techcommunity.microsoft.com/t5/windows-it-pro-blog/sha-1-windows-content-to-be-retired-august-3-2020/ba-p/1544373)
   2. The only affected OSes are Windows 7 and below ([support ended already](https://www.microsoft.com/en-us/windows/end-of-support)). Windows 7 (6.1.7600) users can still upgrade to Windows 7 SP1 (6.1.7601) which supports SHA-2.
   3. Users can still run our app on old Windows systems (Windows 7), despite that the following warning dialog might show up:
![image](https://user-images.githubusercontent.com/93548144/193613642-bf153ea1-d05e-47a2-91b6-73ac2d28ad15.png)
2022-10-11 12:42:36 -04:00
..
jsign-4.2.jar build(manager/electron): 👷 add option to use GCP KMS for signing (#1168) 2022-10-11 12:42:36 -04:00
LICENSE.txt build(manager): 👷 sign Windows apps during electron build (#1104) 2022-06-07 16:21:44 -04:00
METADATA build(manager/electron): 👷 add option to use GCP KMS for signing (#1168) 2022-10-11 12:42:36 -04:00