75
GrapheneOS accessed Android security patches but not allowed to publish sources
(grapheneos.social)
this post was submitted on 11 Sep 2025
75 points (100.0% liked)
Android
20235 readers
529 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
📰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
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I don't understand how in the fuck any of this situation makes sense. We're closing AOSP, but OEMs (Graphene is an OEM now I guess) still get AOSP, but the changes can be reverse engineered... Why? What middle management fuckery is afoot here? Who do we need to be directing hate towards?
probably the OEMs that are slow moving to cut releases.
They don't want to disclose vulnerabilities, because they know most people are not going to upgrade their ancient phone?
Are you being /s? Genuinely, do you really feel just because vulnerabilities aren't publicly exposed they can't be exploited?
I made a guess at their official reasoning for the policy. I made no comment about my own feelings or beliefs beyond that. And no, I don't think that would stop anyone.
Do you have a better guess at why they're doing this? Because I can't think of another reason why they'd be sharing the patches but prohibiting disclosure of them.
Isn't that common to not release how a vulnerability can be exploited publicly until you have it patched? Like yeah it won't stop bad actors familiar with the space, but it would prevent normies like me jumping on the train.