Store a hash of the current index.html for future-proofing

[eeeeeta]

16:31 <lkosov> Also, looking at the code in main.rs, might it be a good idea to future-proof it by either comparing index.html against a local copy of the default, or a hash of the current default? As it is, if the index.html in /etc/skel/public_html ever changes for some reason, it'll throw the script off for pre-existing accounts.

An ideal implementation would assume that there will be different versions of the index.html file and plan for this, by declaring a static array of version numbers and SHA hashes, and potentially exposing this in the resultant users.json output.