[MDEV-24944] mariadb-10.4.18-winx64.msi was not signed timestamp by certification. Created: 2021-02-23  Updated: 2021-03-26  Resolved: 2021-03-26

Status: Closed
Project: MariaDB Server
Component/s: Packaging, Platform Windows
Affects Version/s: 10.4.18
Fix Version/s: 10.2.37, 10.3.28, 10.4.18, 10.5.9

Type: Bug Priority: Major
Reporter: Toshimitsu Nakanishi Assignee: Daniel Bartholomew
Resolution: Done Votes: 0
Labels: None

Issue Links:
Relates
relates to MDEV-24554 Windows authenticode signing stopped ... Closed

 Description   

mariadb-10.4.18-winx64.msi was singed by digital certification.
but, no timestamp signed.

Please, check and fix it.



 Comments   
Comment by Vladislav Vaintroub [ 2021-02-23 ]

it is MDEV-24554 . The old public timestamping service (verisign) stopped working.
the new one (globalsign) did not work very reliably, often failed, so I switched it timestamping for now.

Comment by Daniel Bartholomew [ 2021-02-24 ]

Assigning to wlad for now until issues with the build setup are fixed. Then it can be assigned back to me to make fixed release builds.

Comment by Vladislav Vaintroub [ 2021-03-15 ]

dbart, if you want to rerelease 10.2-10.5, this should work now.

Comment by Daniel Bartholomew [ 2021-03-23 ]

I've rebuilt the 10.2.37, 10.3.28, 10.4.18, and 10.5.9 winx64 and win32 packages, and uploaded them to the primary mirror. The other mirrors should have them soon.

viewhero: Please download the updated version and verify that timestamp verification is working. Here is a direct link:

To verify you have the updated build and not the old one, the sha256 checksum of the updated mariadb-10.4.18-winx64.msi package is:

2fa6830dfc37894e73746d040d855f248d3531910c89ebb339731dc216ec35e5  ./mariadb-10.4.18-winx64.msi

Generated at Thu Feb 08 09:33:53 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.