motioneye-project/motioneye 0.44.0b2 on GitHub

The signature authentication method has been replaced with session cookies. For using the API, a session cookie needs to be obtained by doing a POST request to the /login API, with username and password arguments as POST data/parameters. If credentials were correct, a session cookie is returned, which needs to be sent with the actual API requests. The cookie has a 24h lifetime, hence scripts/programs should automatically redo the login loop when receiving a 403.
For remote motionEye cameras exclusively, a HMAC authentication method has been added, generating a signature from a dedicated secret, request URL, nonce, and tight timestamp. This secret is automatically generated for every motionEye instance, and needs to be entered when adding a remote motionEye camera. Implicitly, motionEye v0.44.0 instances cannot work with older versions vice versa, and for now, remote motionEye cameras need to be removed, and readded with the secret. But we aim to expose an input field for the secret in the camera settings panel, so that it can be added and changed, without the need to remove and readd the camera as a whole.
The HTTP basic authentication option has been removed.
Passwords are now enforced for both users: admin and surveillance/normal, and stored as Argon2 hash on the server. Existing SHA1 hashes and plain text passwords are still functional, and migrated automatically on login. Users are asked to apply passwords on login, if none applied yet.

Fixed monitor info text on camera frames being wrapped into double quotes with extra backslash character \"\": #3322 @Marijn0
The input path validation at the backend has been extended, to prevent any kind of escaping the camera data dir: #3324 @MichaIng
The backup/restore feature is now limited to those config files which are actually generated by the web interface: motion.conf, camera-*.conf, prefs.json, and mask-*.pgm. Files that need to be created from console, like motioneye.conf and camera action scripts, are not included, and won't be restored anymore, if present in old backups: #3338 @MichaIng
Several translations have been updated, and an initial addition of the Bulgarian language was done. Many thanks to all @weblate contributors! ❤️