I found a workaround, but do not know if it will mesh up with future updates from Mail-in-a-Box.
The workaround that I use is to edit owncloud.sh and replace the line with the owncloud_hash value.
@pbx_ramdas - Probably not the best idea in general. ownCloud is investigating because to them it appears that there could have been a security compromise of the ownCloud package (e.g. unauthorized attacker could have replaced ownCloud’s true release archive with a compromised one). Ignoring MD5/SHA sums can be dangerous.
It sounds like it could have just been an issue with their build process, but it’s good to heed warnings like these in general, rather than just making them work without verification of their integrity.
installing ownCloud...
sha1sum: WARNING: 1 computed checksum did NOT match
------------------------------------------------------------
Download of https://download.owncloud.org/community/owncloud-8.0.3.zip did not match expected checksum.
Found:
625b1c561ea51426047a3e79eda51ca05e9f978a /tmp/owncloud.zip
Expected:
3192f3d783f81247eaf2914df63afdd593def4e5 /tmp/owncloud.zip
Is it possible to skip the OwnCloud integration (don’t need this feature at all)?
Or if it’s fixed by the OwnCloud developers (hopefully in some days?), can I run
setup/start.sh
again and it will overwrite my settings?
Or should I better delete something before (because of the aborted/failed installation process)?
I pushed version 0.11 of Mail-in-a-Box which updates to ownCloud 8.0.4. Please try that everyone.
If you were on a new installation and got stuck half way through… I believe it is ok to try again (starting from the curl command in the MiaB setup instructions), but I am not really sure.
People that did replace the key in owncloud.sh need to DELETE the owncloud.sh in the /setup folder before updating. The setup will not continue if you have edited this, and deleting it works. (it will just redownload the original working file)