I run NC (v21.0.5) on Debian 10 with Apache 2.4.38 and PHP 7.3.29.
Until yesterday the integrity checks showed no errors, everything was OK.
Today the integrity check tells me that there is an invalid hash for file .htaccess.
Very interesting and astonishing because i do NOT have an .htaccess file.
Error message at the end of this post.
Some suggestions for NC integrity check:
- According to NC official documents integrity checks are not mandatory. OK.
- But in case of integrity errors they prevent updates / upgrades. Is this benefivial for NC users?.
- The integrity checks should be resilient, e.g. NO .htaccess file no hash check for it, hence no wrong error message (see above).
- NC users should have the opportunity to choose which integrity check (among many) be deployed. Please note that NC users know what they need. Hence, no prescription whatsoever is useful.
Why do I NOT use a .htaccess file?
I integrated the whole contents of the official .htaccess file into the /etc/apache2/apache2.conf.
By doing so I avoid that the contents of .htaccess be deployed every time NC is accessed.
It means I have a performance gain with my web server.
The following list covers which files have failed the integrity check. Please read
the previous linked documentation to learn more about the errors and how to fix
[core] => Array
[INVALID_HASH] => Array
[.htaccess] => Array
[expected] => 1b7e58df33e22722670a77dd1f19eb863f277d5ac79d33d5f5d6e8b7a5977223cb78ba58132f991248b13d13eac744649c2d8a72cf5ec711643cf8c7aec5c456
[current] => cf83e1357eefb8bdf1542850d66d8007d620e4050b5715dc83f4a921d36ce9ce47d0d13c5d85f2b0ff8318d2877eec2f63b931bd47417a81a538327af927da3e