Bug 408605 - Asks for way more google account access than it needs
Summary: Asks for way more google account access than it needs
Status: REOPENED
Alias: None
Product: kio-gdrive
Classification: Frameworks and Libraries
Component: general (show other bugs)
Version: unspecified
Platform: Kubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: Elvis Angelaccio
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-06-12 09:41 UTC by Peter Hamberg
Modified: 2019-06-23 17:34 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Peter Hamberg 2019-06-12 09:41:59 UTC
SUMMARY

When I connect my google account to this google drive sync tool, it also asks for access to my youtube, contacts, calendar, hangouts, photos etc.

This isn't really neccessary, and also makes me as a user feel wary - why does it ask for all that access? Surely it only ever needs read and write access to google drive. 

Please change the sync to only ask for permissions to access google drive.
Comment 1 Elvis Angelaccio 2019-06-16 20:11:30 UTC
You can remove the permissions you don't need from Plasma's Online Accounts KCM.
Comment 2 Peter Hamberg 2019-06-17 07:49:28 UTC
I've looked at that, and no, I can't. It has a checkbox for youtube, and one for google drive, but unchecking those does nothing. Still, even if it had worked, it wouldn't have been enough.

because
a) it still asks for calendar, contacts etc access without it being neccessary
b) a big problem is that it asks for all access when you set up the connection, and then you can later constrain it. this doesnt remove the access on the google-account side of things
Comment 3 Peter Hamberg 2019-06-17 08:30:54 UTC
I'm thinking there needs to be one of these https://cgit.kde.org/kaccounts-providers.git/tree/providers/google.provider.in but with only the gdrive scope claims, then this tool could use that provider instead.
Comment 4 Elvis Angelaccio 2019-06-23 17:34:42 UTC
Ah sorry, then we need to fix the KCM.

I don't think we should ship another provider file, it's not going to scale.