Opened 9 years ago

Closed 4 years ago

#739 closed Feature request (fixed)

Generate SHA2-hashsums of setup artifacts created by the build server

Reported by: kopal Owned by: coredevs
Priority: Nice to have Milestone: CrypTool 2.1 BETA 1
Component: MSBuild Keywords:
Cc:

Description

Currently our build server generates a zip-file and a nsis-installer-exe-file. While the exe-file is digitally signed by the build process the zip file is not. So we want to provide SHA2-hashes which are auto-generated by the MSBuild process after generating both files.

The following steps have to be done:

  • adapt build process to have SHA2-hashes generated at the end (for the ZIP-file and for the exe-file)
  • provide these hash in an easy processible file format (text file?)
  • adapt the cryptool 2.0 web page to show the generated hash values to the users visiting the page

Change History (3)

comment:1 Changed 8 years ago by kopal

Milestone: CrypTool 2.0 BETA 10CrypTool 2.0 RELEASE
Type: BugFeature request

comment:2 Changed 7 years ago by Arno Wacker

Milestone: CrypTool 2.0 RELEASECrypTool 2.1 BETA 1

comment:3 Changed 4 years ago by kopal

Resolution: fixed
Status: newclosed

already integrated into the build process

see: https://www.cryptool.org/ct2download/Builds/hashes.xml

Note: See TracTickets for help on using tickets.