389-ds-base

#49913 sha1 checksum for Windows Console does not match with the files downloaded
Closed: wontfix by mreynolds. Opened by dkt.

Closed: wontfix
Reopen Issue

Files in : https://directory.fedoraproject.org/docs/389ds/download.html#rhelcentosepel-rhel-6-rhel-7-centos-6-centos-7

Platform File SHA1SUM
Windows 2008/2012 32-bit 389-Console-1.1.15-i386.msi 772e4691daea66dcdef97cb220d9ae77ab9fbe78

Windows 2008/2012 64-bit 389-Console-1.1.15-x86_64.msi 35ec5bad0d309c334ba8c5e8ac0ab183f004d7fd

For me, the downloaded files have these sha1 checksum:
296fcdd453a837a519611937acae97faabdd5f34 389-Console-1.1.15-i386.msi
7c7902e781f250e5246fef67e1161ec5ca5ca19f 389-Console-1.1.15-x86_64.msi

Indeed, download page lists incorrect checksums.
I've double checked with our internal build system and it shows the same md5sum (not sha1sum) for both 389-Console files as I get by checking it manually:

107c120197fe85ac5dd982c5928f9552  389-Console-1.1.15-i386.msi
32e6b38f92c014499a7634e687e83586  389-Console-1.1.15-x86_64.msi

Looking at the git log for wiki, we had multiple builds with the same file name, but different checksums. Apparently at some point new builds were uploaded, but the download page was not updated. So these files are correct.

In addition, I've uploaded newer version of 389-Console:

$ sha1sum 389-Console-1.1.18-* 
eff6e9c34300fa9bd2141944655925aaf5c0b431  389-Console-1.1.18-i386.msi
39357d69fd45df28657f1f2c73e23dbc552ecd31  389-Console-1.1.18-x86_64.msi
$ md5sum 389-Console-1.1.18-*  
c6ee9b2f129649a5f74bd6a1d5dfa1c6  389-Console-1.1.18-i386.msi
cc6632f7507c33b3aea46590f8caea3b  389-Console-1.1.18-x86_64.msi

https://fedorapeople.org/groups/389ds//binaries/389-Console-1.1.18-i386.msi
https://fedorapeople.org/groups/389ds//binaries/389-Console-1.1.18-x86_64.msi

Metadata Update from @vashirov:
- Custom field component adjusted to None
- Custom field origin adjusted to None
- Custom field reviewstatus adjusted to None
- Custom field type adjusted to None
- Custom field version adjusted to None

Does the MSI being signed by a publisher?
When I tried to use it, Windows 10 got a warning that the publisher is unknown.

Publisher: Unknown publisher

Does the MSI being signed by a publisher?

No, I don't think so.

When I tried to use it, Windows 10 got a warning that the publisher is unknown.
Publisher: Unknown publisher

Yes, I also get this, even with the files downloaded from Customer Portal. If I recall correctly, there was no support for signing exe/msi files in our build system at the time.

Ok noted. I think I would use it if the checksum is correct, thanks.

Metadata Update from @mreynolds:
- Issue assigned to mreynolds

Metadata Update from @mreynolds:
- Issue close_status updated to: fixed
- Issue status updated to: Closed (was: Open)

389-ds-base is moving from Pagure to Github. This means that new issues and pull requests
will be accepted only in 389-ds-base's github repository.

This issue has been cloned to Github and is available here:
- https://github.com/389ds/389-ds-base/issues/2972

If you want to receive further updates on the issue, please navigate to the github issue
and click on subscribe button.

Thank you for understanding. We apologize for all inconvenience.

Metadata Update from @spichugi:
- Issue close_status updated to: wontfix (was: fixed)
Metadata
None
None
None
None
None
None
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.