Md5sum of latest.zip expects nextcloud-11.0.2.zip

Hello everybody, first time poster here so be gentle :wink:

after downloading latest.zip and latest.zip.md5 from Index of /server/releases I ran $USER@$HOST:/path/to/nc $ md5sum -c latest.zip.md5 < latest.zip as instructed by the server installation manual.

The output is:
md5sum: nextcloud-11.0.2.zip: Datei oder Verzeichnis nicht gefunden nextcloud-11.0.2.zip: FEHLSCHLAG bei open oder read md5sum: WARNUNG: die aufgeführte Datei konnte nicht gelesen werden This roughly translates to … file or directory not found … FAILING on open or read … WARNING: the file could not be read

Doing the same with the nextcloud-11.0.2.zip and nextcloud-11.0.2.zip.md5 returns OK

@nickvergessen @jospoortvliet

Arg, I knew it wouldn’t be that simple…

1 Like

I changed the scripts and pinged lukas to update them on the server. Thanks for reporting this issue back!

Releases: https://gist.github.com/nickvergessen/175726ae32b9c9dab80580a908ca36f1/revisions
Dailies: https://gist.github.com/nickvergessen/e78eac9c84cc0e0d91d50723f3e43166/revisions

Script has been updated and executed.

Just a suggestion - AFAIK MD5 isn’t to be viewed as a safe algorithm anymore. How about automatically computing and SHA256 for the release files?

We provide md5, sha256 and sha512 sums, pick whatever you want to verify it.

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.