Some characters are not or badly handled by rclone config when setting the password

[Freeedim]

The associated forum post URL from https://forum.rclone.org

https://forum.rclone.org/t/some-characters-seem-not-to-be-handled-in-passwords/42760/5

What is the problem you are having with rclone?

When entering passwords with Extended ASCII characters in rclone config, some characters may be normalised, which then prevents rclone from connecting to the remote.

What is your rclone version (output from rclone version)

$ rclone version     
rclone v1.64.2
- os/version: debian kali-rolling (64 bit)
- os/kernel: 6.5.0-kali3-amd64 (x86_64)
- os/type: linux
- os/arch: amd64
- go/version: go1.21.3
- go/linking: static
- go/tags: none

Which OS you are using and how many bits (e.g. Windows 7, 64 bit)

Debian, 64 bits

Which cloud storage system are you using? (e.g. Google Drive)

ProtonDrive

The command you were trying to run (e.g. rclone copy /tmp remote:tmp)

rclone ls proton:

A log from the command with the -vv flag (e.g. output from rclone -vv copy /tmp remote:tmp)

Note: the logs below include some additional lines related to the wrong credentials in cache, since it was executed after having changed the password.

$ rclone ls proton: -vv           
<7>DEBUG : rclone: Version "v1.64.0" starting with parameters ["rclone" "lsd" "proton:" "-vv"]
<7>DEBUG : rclone: systemd logging support activated
<7>DEBUG : Creating backend with remote "proton:"
<7>DEBUG : Using config file from "/home/fred/.config/rclone/rclone.conf"
<7>DEBUG : proton drive root link ID '': Has cached credentials
2023/11/07 11:42:12.365736 ERROR RESTY 401 GET https://mail.proton.me/api/core/v4/users: Invalid access token (Code=401, Status=401), Attempt 1
2023/11/07 11:42:12.523031 ERROR RESTY 422 POST https://mail.proton.me/api/auth/v4/refresh: Invalid refresh token (Code=10013, Status=422), Attempt 1
<7>DEBUG : Saving config "client_uid" in section "proton" of the config file
<7>DEBUG : Saving config "client_access_token" in section "proton" of the config file
<7>DEBUG : Saving config "client_refresh_token" in section "proton" of the config file
<7>DEBUG : Saving config "client_salted_key_pass" in section "proton" of the config file
<7>DEBUG : proton drive root link ID '': Cached credential doesn't work, clearing and using the fallback login method
<7>DEBUG : Saving config "client_uid" in section "proton" of the config file
<7>DEBUG : Saving config "client_access_token" in section "proton" of the config file
<7>DEBUG : Saving config "client_refresh_token" in section "proton" of the config file
<7>DEBUG : Saving config "client_salted_key_pass" in section "proton" of the config file
<7>DEBUG : proton drive root link ID '': couldn't initialize a new proton drive instance using cached credentials: failed to refresh auth: failed to refresh auth, de-auth: 422 POST https://mail.proton.me/api/auth/v4/refresh: Invalid refresh token (Code=10013, Status=422)
<7>DEBUG : proton drive root link ID '': Using username and password to log in
2023/11/07 11:42:14.090172 ERROR RESTY 422 POST https://mail.proton.me/api/auth/v4: The password is not correct. Please try again with a different password. (Code=8002, Status=422), Attempt 1
Failed to create file system for "proton:": couldn't initialize a new proton drive instance: 422 POST https://mail.proton.me/api/auth/v4: The password is not correct. Please try again with a different password. (Code=8002, Status=422)

How to use GitHub

• Please use the 👍 reaction to show that you are affected by the same issue.
• Please don't comment if you have no relevant information to add. It's just extra noise for everyone subscribed to this issue.
• Subscribe to receive notifications on status change and new comments.