Android
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
π°Our communities below
Rules
-
Stay on topic: All posts should be related to the Android OS or ecosystem.
-
No support questions, recommendation requests, rants, or bug reports: Posts must benefit the community rather than the individual. Please post to !askandroid@lemdro.id.
-
Describe images/videos, no memes: Please include a text description when sharing images or videos. Post memes to !androidmemes@lemdro.id.
-
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.
-
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.
-
No editorializing titles: You can add the author or website's name if helpful, but keep article titles unchanged.
-
No piracy or unverified APKs: Do not share links or direct people to pirated content or unverified APKs, which may contain malicious code.
-
No unauthorized polls, bots, or giveaways: Do not create polls, use bots, or organize giveaways without first contacting mods for approval.
-
No offensive or low-effort content: Don't post offensive or unhelpful content. Keep it civil and friendly!
-
No affiliate links: Posting affiliate links is not allowed.
Quick Links
Our Communities
- !askandroid@lemdro.id
- !androidmemes@lemdro.id
- !techkit@lemdro.id
- !google@lemdro.id
- !nothing@lemdro.id
- !googlepixel@lemdro.id
- !xiaomi@lemdro.id
- !sony@lemdro.id
- !samsung@lemdro.id
- !galaxywatch@lemdro.id
- !oneplus@lemdro.id
- !motorola@lemdro.id
- !meta@lemdro.id
- !apple@lemdro.id
- !microsoft@lemdro.id
- !chatgpt@lemdro.id
- !bing@lemdro.id
- !reddit@lemdro.id
Lemmy App List
Chat and More
view the rest of the comments
This sounds less like security
And more like a backdoor
Google can already push apps to your phone at will via their remote installation service. How does this create or open a backdoor?
Leaving your keys in memory is the weakness that could potentially let authorities into your phone. This could harm people. If your phone has rebooted, and you haven't logged in yet, there are no keys in memory. That means your data is encrypted at rest.
For the sake of comparison, this was also implemented in iOS 18.
Thanks for the voice of sanity. There are so many people freaked out by basic security measures that it boggles the mind.
Google has broken trust so often, so severely, that it's the default to not trust anything they do, ever.
If they can, they absolutely will leverage basic security measures for their own benefit. And, it isn't like there's no press by governments to backdoor all the things.
So it shouldn't boggle the mind at all. This is what happens when oligarchs and their servants run amok, nobody can trust anything.
I was referring primarily to things that are known to be good security practices and widely known and used already. Keeping data more secure at rest goes with the "don't trust anything or anyone" goal, and if not doing it on Android due to said trust or lack thereof, then GrapheneOS offers it too at least.
Oh, I get it. I'm looking at switching to graphene despite it needing a Google phone.
I'm just saying that people see Google and changes in an article, it's not weird for them to immediately assume something hinky is going on
The before first unlocked state is considered more secure, file/disk encryption keys are in a hardware security module and services aren't running so there is less surface for an attack . When a phone is taken for evidence, it gets plugged into power and goes in a faraday bag. This keeps the phone in an after first unlock state where the encryption keys are in memory and more services that can be attacked are running to gain access.
So hourly reboot is what you're saying
Depending on your threat model
GrapheneOS has had this feature. Unlocking after a reboot is only possible with PIN. Also the RAM is wiped. This increases security and lowers the risk of attackers gaining access. Be it physically or not.
It's more like security theater if the phone doesn't have the latest OS and doesn't have the necessary hardware to block cellbrite in the BFU state
What hardware do android phones not have making them vulnerable to cellbrite?
I dump memory more often than you would think. It's usually not obfuscated or encrypted in any meaningful way even though it is fairly trivial to do so.
It's good practice to scour through any bloatware installed on windows laptops. Since bloatware is generally written by the lowest bidder, you can find all kinds of keys and phone-home urls (sometimes with all the parameters) and other weird things. Just fire up a decent hex editor and search for strings in the dump file. You don't need to know jack about reverse engineering either.
I am often working as reverse engineer professionally and I also feel that mindset is half the battle--a willingness to see everything as data and to look inside to see what is there. Like digital spelunking.
That, 200%!
When I started in computers, years ago, I transitioned from QuickBasic directly into assembly. Ever since then, I can kinda "read the Matrix" (Blond, Brunette, Redhead....) and forget about how confusing a raw binary or how a mess of a dmp looks to someone else. (To me, I really just see patterns and nothing massively complicated.)
"It's just data." - You would be surprised how fuzzy that statement is for some people. It's almost exactly like telling someone who doesn't speak any English that "the sky is blue". It's totally cool though! Learning about the internals of any computer is really just a very long chain of "aha moments" as many concepts aren't intuitive.
I get to spend a surprising amount of time reading and writing assembly. I consider myself so lucky to be able to do this, and it's true that after enough time you start seeing through it. The human mind is excellent at finding and seeing patterns. Code is no exception. It's just another kind of data. Even the different compilers have their own flavor after a while.
Curious to me that you began in Basic; my experience is that people continue to see their first language in other languages for some time, and the best reverse engineers I've met usually start with something unusual. My hypothesis is that when you start in a weird place, it brings all others closer together so that they appear not so different from each other. The distance between the top of the mountain of code and the deepest valley of flat data doesn't seem so great if you start with, say, Lisp and you never considered that lists weren't both code and data.
I come from Matlab, and to this day I can't see memory as anything but matrices.
I taught myself QuickBasic as it was the only thing I knew that was related to copying C64 BASIC out of magazines. (QBasic was packaged with DOS 3.11 I think and I was able to get a full copy of QuickBasic somehow. That was about +30 years ago? Dunno. I was about 12 at the time.) I didn't know what other languages were out there besides TurboPascal. I did learn simple Pascal, but that was a short chapter.
I actually met someone else in the area that was learning to code, and of course, we wanted to write a game. The only way to code for a mouse at the time was to write an INT33 handler, so it kicked off our interest in asm. (I still use asm for MCU stuff on occasion, but it's limited.) I quickly diverged into writing some really nifty.. eh.. "boot sector code" so that kicked off my career in security.
And yeah, it's the same phenomenon for me: I just think in terms of bits and bytes getting shifted around and I still refuse to believe in "magic". (Slight jab at Rust coders there, but in good fun.)
Fast forward to today, I train "kids" fresh out of college as part of my job now. The first thing I do is start giving them weird tasks that require they actually understand how something like an
fopen()actually works.(Funny story. I refused to "show my work" in math class for simple f(x) problems as I viewed it as unoptimized code. Lulz. I was such an autistic dork.)