S3Drive - base 64 decode problem

Hi, every one, i got this problem with S3drive when i'm gonna log in in my proton drive account. can somebody help me with it? s3drive

Hi @ZHAUMIEL, Thanks for your message. Your password is likely provided in the config as plaintext, but instead it needs to be obscured. Please find this answer which should help you setting things up: https://discord.com/channels/1069654792902815845/1418964838260015245/1419211554053947482 Please let me know if this resolved your issue. (edited)

1

where i can run this command of obscuring the password

6:47 PM

?

ZHAUMIEL

where i can run this command of obscuring the password

Normally you would need to install Rclone on your desktop. How did you end up with the config with a plaintext password though? Alternatively You can configure an Rclone back-end (it doesn't matter what really) within S3Drive, then go to Account settings and Enable E2E. Once you provide password it will actually create crypt configuration as a reference. You can then visit Accounts screen and use: Show .ini config on the crypt back-end and it will displayed obscured password which you can use in your custom config.

1

perfect, that's now iḿ gonna install rclone, i just have installed S3drive

thanks Tom, i really didn't understand you about the Rclone obscure command, but finally could understand you, the key was used the obscure password while i'm trying to log in, not the password itself, i thanks you so much

ZHAUMIEL

thanks Tom, i really didn't understand you about the Rclone obscure command, but finally could understand you, the key was used the obscure password while i'm trying to log in, not the password itself, i thanks you so much

Hi @ZHAUMIEL, Sorry for the confusion. Upon further investigation it came to my realization that in fact bug has slipped in one of the previous versions. This issue will be fixed in a next release, so when you configure back-end using S3Drive forms, password and other credentials will be auto-obscured. Initially, I assumed that you must have used a custom .ini configuration or crypt config. My assumption was that this error could not have come from the forms. (edited)