Welcome to the droidymcdroidface-iest, Lemmyest (Lemmiest), test, bestest, phoniest, pluckiest, snarkiest, and spiciest Android community on Lemmy (Do not respond)! Here you can participate in amazing discussions and events relating to all things Android.
The rules for posting and commenting, besides the rules defined here for lemmy.world, are as follows:
1. All posts must be relevant to Android devices/operating system.
2. Posts cannot be illegal or NSFW material.
3. No spam, self promotion, or upvote farming. Sources engaging in these behavior will be added to the Blacklist.
4. Non-whitelisted bots will be banned.
5. Engage respectfully: Harassment, flamebaiting, bad faith engagement, or agenda posting will result in your posts being removed. Excessive violations will result in temporary or permanent ban, depending on severity.
6. Memes are not allowed to be posts, but are allowed in the comments.
7. Posts from clickbait sources are heavily discouraged. Please de-clickbait titles if it needs to be submitted.
8. Submission statements of any length composed of your own thoughts inside the post text field are mandatory for any microblog posts, and are optional but recommended for article/image/video posts.
Community Resources:
We are Android girls*,
In our Lemmy.world.
The back is plastic,
It's fantastic.
*Well, not just girls: people of all gender identities are welcomed here.
Our Partner Communities:
No thanks, sounds like security and privacy nightmare.
The part about "no user interaction required" doesnt feel right secure.
Especially as it is stored at google servers, it says it is encrypted but it is encrypred using keys that google has access to as they are unlocked with you logging in into google account.
Aren't they encrypted with the phone's lockscreen password? You very much need that to restore cloud backups. Not that it has much value if you're a 4 digit PIN person...
Anyway, I can use a search engine:
Some data is further encrypted with your device’s screen lock. Photos and videos stored in Google Photos, and MMS media received from your carrier are not encrypted by your device’s screen lock.
Well, what is some data?
Anyway, I wish for something universal for offline backups. I mean, without root.
It's only stored with Google if cloud backup is enabled it says. Otherwise, the keys are transferred along with all the other data directly from device to device when switching.
it says it is encrypted but it is encrypred using keys that google has access to as they are unlocked with you logging in into google account.
First it uses lock screen password, so google do not have access to this password.
Even if your lock screen is unfortunately your Google password, I think proper authentication protocol do not send your password to Google to authenticate, but only the hash, which cannot be reverted to derive your password.
Obviously, the above is assuming that Google is not malicious. Otherwise it can just use play service, which is privileged and closed source, to get all your data. If your threat model including Google itself trying to steal your key, you will probably need to install a trusted rom or use iOS (however, apple and the rom developer can also steal your key).
assuming that Google is not malicious
Previously they would need to push malicious code to your device to steal your login data, that is a risk that someone would do reverse engineering on that and expose it, now they will have the data on their servers and they can abuse it any time they want, I doubt they will use it to login as you, but they will use it as metadata to connect all your accounts for marketing.
proper authentication protocol do not send your password to Google to authenticate
That is not true for 99% services including google. Google have a plain text password at the time you are logging in, they just store hashed+salted version in storage.
(Almost) No website (or app) is hashing the password before sending it to server, so if you hack the login screen you can dump RAW passwords anytime.
You are right. I have done some research, it seems most people think that client side hashing is unnecessary in an HTTPS setting.
That is my misunderstanding.
They should enable ability to do local backups.