Opened 4 weeks ago

Last modified 4 weeks ago

#2403 new defect

Signing corrupts the windows installer

Reported by: zab Owned by:
Priority: minor Milestone: 0.9.39
Component: installer Version: 0.9.38
Keywords: Cc:
Parent Tickets:

Description

Signing the windows installer with signtool causes the installer to become corrupt. Possible solution outlined here https://stackoverflow.com/questions/22325009/sign-a-launch4j-executable-in-ant-with-sign4j-and-jsign but that would require either building the installer on a windows machine, and I'm not sure signtool can be invoked outside of a developer command prompt.

Other options include:

  • leave the windows installer unsigned
  • move away from launch4j, either via izpack's binary or jlink (i2p-zero)

Subtickets (add)

Change History (1)

comment:1 Changed 4 weeks ago by zzz

  • Milestone changed from undecided to 0.9.39

Would be nice to figure this out for 39, but will take some time to research and test the options.

I've never looked closely at the izpack exe tools (on either izpack 4 or 5), launch4j was in place before my time, 15 years ago.

Note: See TracTickets for help on using tickets.