this post was submitted on 03 Aug 2023
35 points (100.0% liked)

Privacy Guides

16784 readers
55 users here now

In the digital age, protecting your personal information might seem like an impossible task. We’re here to help.

This is a community for sharing news about privacy, posting information about cool privacy tools and services, and getting advice about your privacy journey.

You can subscribe to this community from any Kbin or Lemmy instance:

Learn more...

Check out our website at privacyguides.org before asking your questions here. We've tried answering the common questions and recommendations there!

Want to get involved? The website is open-source on GitHub, and your help would be appreciated!

This community is the "official" Privacy Guides community on Lemmy, which can be verified here. Other "Privacy Guides" communities on other Lemmy servers are not moderated by this team or associated with the website.

Moderation Rules:

  1. We prefer posting about open-source software whenever possible.
  2. This is not the place for self-promotion if you are not listed on privacyguides.org. If you want to be listed, make a suggestion on our forum first.
  3. No soliciting engagement: Don't ask for upvotes, follows, etc.
  4. Surveys, Fundraising, and Petitions must be pre-approved by the mod team.
  5. Be civil, no violence, hate speech. Assume people here are posting in good faith.
  6. Don't repost topics which have already been covered here.
  7. News posts must be related to privacy and security, and your post title must match the article headline exactly. Do not editorialize titles, you can post your opinions in the post body or a comment.
  8. Memes/images/video posts that could be summarized as text explanations should not be posted. Infographics and conference talks from reputable sources are acceptable.
  9. No help vampires: This is not a tech support subreddit, don't abuse our community's willingness to help. Questions related to privacy, security or privacy/security related software and their configurations are acceptable.
  10. No misinformation: Extraordinary claims must be matched with evidence.
  11. Do not post about VPNs or cryptocurrencies which are not listed on privacyguides.org. See Rule 2 for info on adding new recommendations to the website.
  12. General guides or software lists are not permitted. Original sources and research about specific topics are allowed as long as they are high quality and factual. We are not providing a platform for poorly-vetted, out-of-date or conflicting recommendations.

Additional Resources:

founded 1 year ago
MODERATORS
jonah@lemmy.one
dngray@lemmy.one
freddy@lemmy.one
ninchuka@lemmy.one
jonah@lemmy.jonaharagon.net
35
Proton Drive backend on Rclone beta (sh.itjust.works)
submitted 1 year ago* (last edited 1 year ago) by lasagna@sh.itjust.works to c/privacyguides@lemmy.one
2 comments fedilink hide all child comments
 

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 are viewing a single comment's thread
view the rest of the comments
[–] tau@discuss.tchncs.de 7 points 1 year ago* (last edited 1 year ago)

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.