In order to have all relevant examples in this thread, I'm repeating the download errors reported in the CEP2 beta test July 25, 2016 [Issues Thread]. These were wingmen's results, so I don't have the Event Logs.

Here's a -119 error:
BETA_ E236441_ 40_ S.400.C56F1H25N2S1.LOUQHRXRTVLJRV-UHFFFAOYSA-N.2_ s1_ 14_ 1--
<core_client_version>7.6.22</core_client_version>
<![CDATA[
<message>
WU download error: couldn't get input files:
<file_xfer_error>
<file_name>beta11.CleanEnergyProjectLogo_2.tga</file_name>
<error_code>-119 (md5 checksum failed for file)</error_code>
<error_message>MD5 check failed</error_message>
</file_xfer_error>

and a -120 error (actually, two -120 errors for the same workunit):
BETA_ E236441_ 854_ S.396.C44F2H20N2S5.WYRHUGMFRDHYMU-UHFFFAOYSA-N.1_ s1_ 14_ 1--
<core_client_version>7.6.22</core_client_version>
<![CDATA[
<message>
app_version download error: couldn't get input files:
<file_xfer_error>
<file_name>wcgrid_beta11_qchem_prod_win32.exe.7.00</file_name>
<error_code>-120 (RSA key check failed for file)</error_code>
</file_xfer_error>
<file_xfer_error>
<file_name>cep2_image02_7.00.tga</file_name>
<error_code>-120 (RSA key check failed for file)</error_code>
</file_xfer_error>

Got a resend HSTB. Immediate error:
<core_client_version>7.6.22</core_client_version>
<![CDATA[
<message>
app_version download error: couldn't get input files:
<file_xfer_error>
<file_name>wcgrid_hst1_gromacs_7.14_windows_x86_64</file_name>
<error_code>-120 (RSA key check failed for file)</error_code>
</file_xfer_error>
</message>

The >30 HSTB's before all went fine.

I've reset the cache again, hopefully you can download it now.

We are looking into alternatives to using the CDN.

The issue is not whether one can "download it". The issue is that the md5 checksum is not verifying after one downloads it. I get a different (and wrong) md5 checksum every time I download the software from worldcommunitygrid.org.

With all due respect, I am not going to recommend to others that they join this project if I am not confident that the software they are downloading has integrity.

Until such time that the website admin can guarantee that the end user is downloading the correct, cryptographically verifiable file, the download links should be disabled.

@we4qcphi8, Hi, and welcome to WCG and the forum!

A problem with your idea of disabling a download link is that most WCG members are not experiencing the -119 or -120 errors most of the time. If the MD5 or RSA Key check fails, then the file is rejected by your client software, so the integrity of any downloaded software that is available to run is still assured.

More than one file has been reported as giving the problem. It might help the WCG techs with further information if you post details from the Event Log when the problem occurs for you. Adding the file_xfer_debug flag for logging might also help (in later BOINC versions, use Options / Event Log Options; otherwise, ask).

A basic premise of BOINC and WCG is that the whole procedure can be set and forget, so a manual MD5 check is not an option.