However, when I click on the link, I get this:
Code: Select all
Verify Installation Integrity
Unable to compare checksums! (No checksums.inc.php in main directory)1.4 -> Verify installation integrity error
-
Don Chambers
- Regular
- Posts: 3657
- Joined: Mon Feb 13, 2006 2:40 am
- Location: Chicago, IL, USA
- Contact:
1.4 -> Verify installation integrity error
I upgraded one of my sandboxes to 1.4beta a week or 2 ago, and just happened to notice this new admin option. Docs suggest Judebert may have had a hand in this new functionality.
However, when I click on the link, I get this:
When should the file checksums.inc.php have been created? I upgraded from a 1.3.x branch.
However, when I click on the link, I get this:
=Don=
-
Don Chambers
- Regular
- Posts: 3657
- Joined: Mon Feb 13, 2006 2:40 am
- Location: Chicago, IL, USA
- Contact:
The checksums would be created when the release is created. The create_release.sh script in the bundled-libs/ directory does the trick.
If you upgraded from an SVN checkout, it wouldn't have the checksums. You could create them yourself, of course.
For you and others like you, I've created a checksum ZIP for the latest s9y trunk (9/9/08, revision 2332). Just unzip it and put the resulting checksums.inc.php in your blog directory (by default, serendipity/).
Note that the checksums are used only for verification, and will cause no change in behavior at all. They are used merely to see what has been changed since the checksums were generated, and print a reassuring (or terrifying) message for the administrator.
The idea is that, at some point in the future, all versions of Serendipity will be released with a checksum file. If the integrity check indicates that files have been changed, you should know why. Could be you changed them yourself, could be a bad upload, or it could be hacker. Either way, you know. And when you need help on the forum, you can check for bad uploads and modified files.
If you need another checksum zip, let me know.
If you upgraded from an SVN checkout, it wouldn't have the checksums. You could create them yourself, of course.
For you and others like you, I've created a checksum ZIP for the latest s9y trunk (9/9/08, revision 2332). Just unzip it and put the resulting checksums.inc.php in your blog directory (by default, serendipity/).
Note that the checksums are used only for verification, and will cause no change in behavior at all. They are used merely to see what has been changed since the checksums were generated, and print a reassuring (or terrifying) message for the administrator.
The idea is that, at some point in the future, all versions of Serendipity will be released with a checksum file. If the integrity check indicates that files have been changed, you should know why. Could be you changed them yourself, could be a bad upload, or it could be hacker. Either way, you know. And when you need help on the forum, you can check for bad uploads and modified files.
If you need another checksum zip, let me know.