fix: log in with the password on servers that refuse tokens
Nextcloud Music answers a token login with Subsonic error 41, so remus could not log in to it at all. Login now retries with the password, hex-encoded as the spec allows, when the server returns 41, and saves which method worked. Servers that accept tokens are unaffected, and existing login files still load. Server errors now keep their code. A wrong password on Nextcloud adds a line about the API password from the Music app's settings, which is not the Nextcloud login password.
This commit is contained in:
@@ -19,6 +19,8 @@ cargo run --release -- --windowed
|
||||
|
||||
On first start remus asks for the server address, username and password. It stores the address, the username and an auth token (md5 of password + salt) in `~/.config/remus/config.toml`, mode 0600. The token is enough to log in to that server, so treat the file as a credential. Delete it to log in again.
|
||||
|
||||
Some servers refuse token logins (Subsonic error 41), Nextcloud Music among them. For those remus logs in with the password itself and stores that in `config.toml` instead of a token, still mode 0600. Nextcloud Music wants the API password generated in its Music settings, not the Nextcloud login password.
|
||||
|
||||
Covers are cached in `~/.cache/remus/covers`.
|
||||
|
||||
## Install on SteamOS
|
||||
|
||||
Reference in New Issue
Block a user