51
top 16 comments
sorted by: hot top controversial new old
[-] MishaalRahman@lemdro.id 10 points 1 year ago

Let me know if you have any feedback about this article 😁

[-] winterpeacock@discuss.tchncs.de 5 points 1 year ago

I don’t know the exact reason why Android requires the primary user to enter their PIN/password before any other user can log in, but it may be due to the fact that the primary user is also the “system” user which is “always running even when other users are in the foreground.

Full disk encryption?

[-] MishaalRahman@lemdro.id 5 points 1 year ago

Android hasn't used FDE for a couple of years now. File Based Encryption (FBE) has been required instead since Android 10. With FBE, each user has their own credential encrypted storage location for apps, which are encrypted with the credential from that particular user. (I verified this while testing. When you boot and unlock the primary user, other users data at /data/user/{id} is still encrypted until you unlock them.)

[-] winterpeacock@discuss.tchncs.de 0 points 1 year ago

Maybe there are other system files required that are encrypted with the primary user credentials

[-] MishaalRahman@lemdro.id 2 points 1 year ago

There might be, though I couldn't find any. I poked around /data on a rooted Pixel that had just booted but hadn't had its primary user unlocked yet, and I was able to access most files in /data/system still.

[-] someone_secret@burggit.moe 1 points 1 year ago

Pretty much my thoughts, yes.

In order for the FDE to have any usefulness, the key has to be derived from a secret that only the user of phone knows (I.e. a secret PIN, password or pattern)

[-] MishaalRahman@lemdro.id 3 points 1 year ago

Android devices stopped using FDE a while back. In fact, support for FDE was removed entirely in Android 13.

[-] someone_secret@burggit.moe 1 points 1 year ago

Sorry, but that's not true. While technically true, that full disk encryption doesn't exist anymore, they use file based encryption which, functionally, is the same thing. Source: https://www.androidauthority.com/how-to-encrypt-android-device-326700/

[-] MishaalRahman@lemdro.id 4 points 1 year ago* (last edited 1 year ago)

File based encryption is not functionally "the same thing". The AOSP documentation explains how FBE works much more accurately.

[-] Zectivi@lemmy.world 9 points 1 year ago

I didn't know that Samsung had that feature, but it does sound nice - so long as you have the ability to enable maintenance mode.

I recently took my pixel 7 in to ubreakifix for a screen replacement. The screen was 100% dead, but I could still hear the notifications coming in. I couldn't put it into maintenance mode if it had one, so I think I'd still stress a bit about whether or not the phone would be wiped, such as in the case I was unable to verify the upload of a recent Aegis backup. It would be nice if the maintenance mode was able to be triggered via a web interface in cases such as mine. Or maybe even a specific button combo that would be difficult to accidentally do.

[-] MishaalRahman@lemdro.id 8 points 1 year ago

That's a good point, and I agree: There should be a way to trigger Maintenance Mode remotely, like through Find My Device, should Google implement this.

[-] TrenchcoatFullofBats@belfry.rip 4 points 1 year ago

Good article, thanks for writing and sharing here!

I'm not an Android developer, but I do know Linux, and it sounds like Samsung's maintenance mode could just be another user with different permissions, with access to system directories but not user home directories.

If, as you say, Google gives the primary user full rights (like having admin rights in Windows), that would mean that Samsung might be creating "regular" users without those rights, and "maintenance mode" could simply be another regular user - by default, regular users don't have access to other regular user's home directories.

[-] Moonrise2473@feddit.it 3 points 1 year ago* (last edited 1 year ago)

Theoretically, isn't maintenance mode completely useless?

If they're the manufacturer, they could upload and boot via fastboot a signed image that allows all tests to be done, all automatically

When I broke the screen of my Xiaomi mix 3, it was completely black, I sent it back to repair and they had no problem at all repairing it even if I didn't unlock it before sending it. (Maybe it's because Xiaomi has hw tests shortcuts in the bootloader?)

[-] MishaalRahman@lemdro.id 4 points 1 year ago

Sure, the manufacturer could, but they might not provide those kinds of images to their official repair centers, certainly not third-party ones.

[-] Moonrise2473@feddit.it 1 points 1 year ago

They should provide it, easier to do compared to a mode that can't be activated if the screen is broken or simply the user has no idea how to do it.

For example Epson gives watermarked service programs to authorized service centers (splash screen says "licensed to Mr xxx of yyy inc." so they know exactly who leaked it)

Apple also has such secret software

This will also give a competitive advantage to official service centers (why pay $$$ for certification and training if can get the same tools of a generic store that opened yesterday?)

[-] CatherineHuffman@burggit.moe 1 points 1 year ago

Google should be embarrassed at how much better Samsung is.

load more comments
view more: next ›
this post was submitted on 09 Jul 2023
51 points (100.0% liked)

Android

17668 readers
47 users here now

The new home of /r/Android on Lemmy and the Fediverse!

Android news, reviews, tips, and discussions about rooting, tutorials, and apps.

🔗Universal Link: !android@lemdro.id


💡Content Philosophy:

Content which benefits the community (news, rumours, and discussions) is generally allowed and is valued over content which benefits only the individual (technical questions, help buying/selling, rants, self-promotion, etc.) which will be removed if it's in violation of the rules.


Support, technical, or app related questions belong in: !askandroid@lemdro.id

For fresh communities, lemmy apps, and instance updates: !lemdroid@lemdro.id

💬Matrix Chat

💬Telegram channels / chats

📰Our communities below


Rules

  1. Stay on topic: All posts should be related to the Android OS or ecosystem.

  2. No support questions, recommendation requests, rants, or bug reports: Posts must benefit the community rather than the individual. Please post to !askandroid@lemdro.id.

  3. Describe images/videos, no memes: Please include a text description when sharing images or videos. Post memes to !androidmemes@lemdro.id.

  4. No self-promotion spam: Active community members can post their apps if they answer any questions in the comments. Please do not post links to your own website, YouTube, blog content, or communities.

  5. No reposts or rehosted content: Share only the original source of an article, unless it's not available in English or requires logging in (like Twitter). Avoid reposting the same topic from other sources.

  6. No editorializing titles: You can add the author or website's name if helpful, but keep article titles unchanged.

  7. No piracy or unverified APKs: Do not share links or direct people to pirated content or unverified APKs, which may contain malicious code.

  8. No unauthorized polls, bots, or giveaways: Do not create polls, use bots, or organize giveaways without first contacting mods for approval.

  9. No offensive or low-effort content: Don't post offensive or unhelpful content. Keep it civil and friendly!

  10. No affiliate links: Posting affiliate links is not allowed.

Quick Links

Our Communities

Lemmy App List

Chat and More


founded 1 year ago
MODERATORS