VPN issue at Android?

cdflasdkesalkjfkdfkjsdajfd

I've read about that and asking if GrapheneOS is also exposed or not. Thanks

"
Google has known about a bug that breaks VPN apps for 7 months, leaving users exposed with no warning or error, just a VPN app that stopped working in the background.

If you're using ANY VPN on Android, you can help us by getting Google's attention to fix it.

The bug corrupts Android's network stack at the system level after a VPN update, causing users to blame their VPN provider.

Restarting the app doesn't help, with the only fix being a full device reboot or VPN app reinstall, something which most users never figure out.

This affects several VPN providers on Android 16, and only Google has the access to diagnose it properly.

After 7 months of waiting, we're now asking publicly: Google, when are you fixing this?

Issue Tracker Links:

https://issuetracker.google.com/issues/441315112 and
https://issuetracker.google.com/issues/447433152

de0u

cdflasdkesalkjfkdfkjsdajfd I've read about that and asking if GrapheneOS is also exposed or not.

I don't speak for the GrapheneOS project, but my understanding is that the project has released some fixes for VPN leaks (source source) and is working to detect and hopefully remediate others.

userofgos

cdflasdkesalkjfkdfkjsdajfd see here: https://xcancel.com/GrapheneOS/status/2034413241946829258#m

The issue you're describing is not a VPN leak but rather is properly blocked by the leak blocking feature. We've also identified that it's caused by apps using a protected socket feature in a certain way and it's something they can avoid.

It's not always due to apps misusing anything. There are bugs in the protected socket APIs. GrapheneOS has fixes for the most severe VPN leaks already and we're working on finishing up resolving all remaining issues. We can resolve this annoyance (not a leak) alongside that.

And here: https://xcancel.com/GrapheneOS/status/2034412540520718785#m

GrapheneOS has leak blocking enabled by default. Since that's the default, these kinds of issues where the VPN fails to start / connect aren't a privacy issue for GrapheneOS. It's only an annoyance and we're going to eventually determine what causes this rare issue to fix it

We already have fixes for 5 holes in Android's VPN leak protection. We're working on identifying all remaining issues and resolving those. The most severe issues are fixed but there are remaining bugs in the Android VPN APIs we need to resolve. It's a lot of work and not easy.

Our priority is fixing leaks rather than an issue causing an annoyance where a reboot might be required to get connectivity again since leak blocking is working properly for it. We have 1 full-time developer mainly working on resolving VPN issues right now. We can't assign more.

Our priority is fixing the leaks rather than an issue causing an annoyance where a reboot might be required to get connectivity again which is successfully blocked by the VPN leak protection. Google has far more resources. It's inherently slow for us to get a dozen bugs fixed.