As a consequence of making the android and iPhone apps open source, they have been able to create a backend for Proton Drive on rclone beta.
This is cool for things that I have stored on a Linux machine but am I correct in feeling wary of using this from a security standpoint until Proton creates their own public API?
I’m comparing this to how Google requires you to authenticate yourself via OAuth for security vs how this is asking you to put in your Proton username and password and 2FA and it gets stored as a token in the config file.
I’m just a layman. Just trying to see if my understanding is correct and if there’s other things to think about.
What do you think? Is there anything else to consider? Will you use this rclone backend to Proton for yourself? Am I too skeptical?
You must log in or register to comment.
am I correct in feeling wary of using this from a security standpoint
I don’t really think you have to be worried about security. Without an official API I’d be more worried about stability and potential data loss due to e.g. bugs in the encryption implementation or unexpected API changes though.
this is asking you to put in your Proton username and password and 2FA and it gets stored as a token in the config file.
As far as I can tell it’s just using your username and password to obtain an access token just like any other Proton Drive client, including the offical one, would have to do.
I’m comparing this to how Google requires you to authenticate yourself via OAuth for security vs how this is asking you to put in your Proton username and password and 2FA and it gets stored as a token in the config file.
Without disk encryption it is a problem if your pc/laptop is at risk of being stolen. With disk encryption it is a problem if an attacker has physical access while the computer is powered on.
