Inconsistencies in some of the files released for version 1.26.20.

[H-andy]

These are admin issues rather than an operational ones.

"VeraCrypt Portable 1.26.20.exe", "VeraCrypt Setup 1.26.20.exe" & "VeraCrypt User Guide.chm".

The naming of these files is inconsistent for those on Github when compared to the same on Launchpad or Sourceforge, i.e. there are "." instead of spaces in the filenames on Github.

The "VeraCrypt.Portable.1.26.20.exe", "VeraCrypt.Setup.1.26.20.exe" & "VeraCrypt.User.Guide.chm" files downloaded from Github should be consistent in name with those on Launchpad and Sourceforge so as to pass hash verification, i.e. spaces instead of "." in their names.

Whilst the filenames name be edited in the hash files this breaks hash file verification with the relevant pgp signature.

For future releases of these files an underscore or hyphen instead of a space may be better in their filenames across all release platforms for greater consistency.

"VeraCrypt_1.26.20_Bundle.7z.checksums" & "VeraCrypt_1.26.20_Bundle.7z.checksums.sig"

These files have not been published on Github, Launchpad or Sourceforge.

There are links to these files on "https://www.veracrypt.fr/en/Downloads.html" but they do not resolve to anything on Launchpad.

Generate and publish "VeraCrypt_1.26.20_Bundle.7z.checksums" or "VeraCrypt_1.26.20_Bundle.7z.checksums.sig" on all sites or remove links from download webpage.

Thanks for all your efforts.

[idrassi]

Thank you for the feedback.

I have fixed the broken links for the bundle checksums file: it was created but it was not uploaded. Now it is available. It was also missing from Sourceforge and Github so I put it there too.

Indeed, Github misses up with spaces and adds dots. Packages were never uploaded to Github until 3 years ago and Github is not the main distribution channel. That's why this problem was not a priority.

I agree that it is creating inconsistencies and issues. The presence of spaces is Windows related files is historical and it was kept for compatibility and consistency for the past 12 years. I'm willing to change space to underscore but in order to avoid breaking existing scripts and flows we should keep copies that uses spaces in naming during a transition period.

I will implement this.