Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

GrapheneOS fixes Android VPN leak Google refused to patch

cyberinsider.com

Post reply on HN
Print view View original

91–100 of 142 posts

Re: GrapheneOS fixes Android VPN leak Google refused to patch

#91

Post by amarant »

surgical_fire wrote: post #14
snapplebobapple wrote: post #10

Earlier quoted context omitted.

First motorola grapheneos phone i am buying to get fully off the google pain train. Grapheneos tides me over until a real linux smart phone shows up or i die of old age. Now if home assistant could get thread network join*ng working without an android phone with a google account i could ve fully ris of those eh holes.

I am patiently waiting for that one. I have been willing to move to GrapheneOS for a while, but I don't feel like buying Google hardware.

Fwiw the pixel phones are excellent hardware.

Re: GrapheneOS fixes Android VPN leak Google refused to patch

#92

Post by amarant »

sfRattan wrote: post #81
thrownthatway wrote: post #70

Earlier quoted context omitted.

Isn’t part of the point of wanting GrapheneOS is that the official support periods don’t matter?

Graphene OS only supports devices for as long as the manufacturer is providing security updates for the phone's firmware. Firmware is binary blob, so there'd be no practical way for anyone else to provide/develop security updates once the manufacturer is no longer providing official updates. Their partnership with Motorola, I think, involves some ability of Graphene OS devs to access/harden/update the firmware, but I…

It can be done, fairphone rather famously did it once.

But it is vastly uneconomical, and I doubt anyone is going to start doing it regularly.

We really need some kind of regulation demanding firmware support for longer. The EU seems the most likely entity to achieve something like that. Phone vendors can't even control how long they support their own hardware, because the SoC is almost always Qualcomm, and once they drop support, there aren't any good options left.

Re: GrapheneOS fixes Android VPN leak Google refused to patch

#93

Post by thrownthatway »

sfRattan wrote: post #81
thrownthatway wrote: post #70

Earlier quoted context omitted.

Isn’t part of the point of wanting GrapheneOS is that the official support periods don’t matter?

Graphene OS only supports devices for as long as the manufacturer is providing security updates for the phone's firmware. Firmware is binary blob, so there'd be no practical way for anyone else to provide/develop security updates once the manufacturer is no longer providing official updates. Their partnership with Motorola, I think, involves some ability of Graphene OS devs to access/harden/update the firmware, but I…

Ah righteo. Thanks for updating my understanding.

Re: GrapheneOS fixes Android VPN leak Google refused to patch

#94

Post by [deleted] »

1vuio0pswjnm7 wrote: post #56

"In its latest release, GrapheneOS says it has "disable[d] registerQuicConnectionClosePayload optimization to fix VPN leak," effectively neutralizing the attack vector on supported Pixel devices." "GrapheneOS responded by disabling the underlying optimization entirely in release 2026050400." GrapheneOS "fixed" the leak by disabling the optimisation Some HN commenters in the past have praised QUIC and downvoted commen…

[deleted]

Re: GrapheneOS fixes Android VPN leak Google refused to patch

#95

Post by Mhatesmisinfo »

jona-f wrote: post #51

I bought a used Pixel 6 for cheap to try out grapheneos. Can't say I like it. UX of lineageos is much better. There is a weird russian doll kind of situation with the package managers going on. There is one builtin "App Store" with only a few basis programs, one of which is another package manager, accrescent, which offers a few more apps, but still not comprehensive at all, so another package manager is needed for w…

F droid is known to be highly insecure. It has many many bad practises that totally compromise security and they have proven to be woefully incompetent and ignorant to concepts as basic as the purpose of app signing.

The all apps stemming from app stores in the builting App Store is to provide a minimalist experience by default whilst keeping google play apps accessible. GrapheneOS has a majour focus on accessibility. They avoid users having to be technical to install an app store to get their apps.

Re: GrapheneOS fixes Android VPN leak Google refused to patch

#96

Post by strcat »

mystifyingpoi wrote: post #43
fg137 wrote: post #39

Side question: what's a good way of getting a GrapheneOS phone? I have been interested in using GrapheneOS but hesitant about actually getting a Pixel phone. Used phone prices are usually >$300 even for "a" series unless I go back several generations. Whether the device bootloader can be unlocked is also a question. I am definitely not ready to spend $449 on a new Pixel 10a.

Don't buy Pixel 10a, 9a is almost exactly the same thing and still sold new.

Pixel 10a is essentially a proper Pixel 9a. It uses the Pixel 9 SoC and Pixel 9 cellular radio compared to the Pixel 9a using the cellular radio used by 8th gen Pixels. The 9th gen Pixel cellular radio was a huge upgrade for connectivity and power efficiency so it's a major advantage for the Pixel 10a over the Pixel 9a. They're budget devices and definitely have significant compromises for the display, wireless charging and other areas.

Re: GrapheneOS fixes Android VPN leak Google refused to patch

#97

Post by HybridStatAnim8 »

mcraiha wrote: post #8
k4rli wrote: post #5

Earlier quoted context omitted.

Interestingly GrapheneOS being so good brings more money to Google as only Pixel phones are supported.

There should be at least one Motorola phone before end of the year that has GrapheneOS support.

Motorola devices with GrapheneOS support will arrive in 2027 or later, not 2026. Likely, the 2027 Signature, Razr fold, and Razr flip, will meet GOSs hardware security requirements.

Re: GrapheneOS fixes Android VPN leak Google refused to patch

#98

Post by HybridStatAnim8 »

neilv wrote: post #22
winter_blue wrote: post #13

Earlier quoted context omitted.

Sadly, Verizon Pixel phones, even after carrier unlocking, seem to be forever blocked from using GrapheneOS.

Carrier-sold Pixels generally don't have "OEM-unlockable" bootloaders. Your best bet for now is to buy a new Pixel direct from Google, or a used one from eBay that the seller advertises as already having GrapheneOS on it (or otherwise guarantees that the bootloader is unlockable). These ones are worth a lot more than the ones that can only run Google/carrier Android. https://grapheneos.org/install/web#prerequisites I…

OEM/carrier locking tends to only happen in the US. Many carriers permit unlocking after the contract has concluded, but Verizon has always blocked it. Used devices also run the risk of being improperly unlocked and making OEM unlocking remain unavailable. (Used devices may also be Verizon devices.)

Re: GrapheneOS fixes Android VPN leak Google refused to patch

#99

Post by HybridStatAnim8 »

winter_blue wrote: post #90
neilv wrote: post #22

Earlier quoted context omitted.

Carrier-sold Pixels generally don't have "OEM-unlockable" bootloaders. Your best bet for now is to buy a new Pixel direct from Google, or a used one from eBay that the seller advertises as already having GrapheneOS on it (or otherwise guarantees that the bootloader is unlockable). These ones are worth a lot more than the ones that can only run Google/carrier Android. https://grapheneos.org/install/web#prerequisites I…

Is this true for all carriers? Or just Verizon? Several Reddit threads say that it's just Verizon. T-Mobile users report being able to bootloader unlock after getting their phones carrier unlocked by T-Mobile.

OEM/carrier locking tends to only happen in the US. Many carriers permit unlocking after the contract has concluded, but Verizon has always blocked it. Used devices also run the risk of being improperly unlocked and making OEM unlocking remain unavailable. (Used devices may also be Verizon devices.)

Re: GrapheneOS fixes Android VPN leak Google refused to patch

#100

Post by HybridStatAnim8 »

fg137 wrote: post #39

Side question: what's a good way of getting a GrapheneOS phone? I have been interested in using GrapheneOS but hesitant about actually getting a Pixel phone. Used phone prices are usually >$300 even for "a" series unless I go back several generations. Whether the device bootloader can be unlocked is also a question. I am definitely not ready to spend $449 on a new Pixel 10a.

An 8 series device or higher is recommended. Getting new from non-carrier stores or google store is reliable.

Used is a gamble due to improper OEM unlocking practices, so make sure it has a good return policy and try to verify OEM unlocking is accessible if you purchase used.

Post reply on HN