Version consistency

[d.walenczak]

Hey guys,

I noticed that we have some inconsistencies with our versioning practice. I just updated to the latest version on the Git. It seems that is labelled at 3.44.2. However, the version in the installer (and what is reflected post install) is 3.44.1. I think that's just a matter of updating the version indicated in the installer itself, which should propagate to TicketCAD itself upon install.

I know we've had some changes that didn't result in a subsequent increase in the patch version number. I was wondering if there were thoughts about standardizing what results in a new release version vs. what is just a GitHub update for a dev version?

I was also thinking about a process during the install to upgrade existing passwords to bcrypt. If the password formatting doesn't match that of bcrypt, bcrypt the legacy password (regardless of the method previously used). It would result in those passwords being double-hashed, but on the bright side. However, it would mean that legacy passwords won't still be vulnerable until that user eventually logs in. On initial login, if it passes as just bcrypt, it proceeds with the login without anything further. If it passes as a bcrypt of the sha1, md5, or other hashing algorithm, then still process the login, but update the password with the bcrypt of just the password itself. Or, potentially, we could use an online API to decrypt md5 hashed passwords during the install and then hash them with bcrypt -- if an online connection is available.