LOL if that's the fix and the Android Security team won't fix it... jfc what a joke
I have a bunch of android based barcode scanners at work that we have to use adb to do some of the configuration setup. it's a powerful tool but it's not rocket science or anything more complicated than command line stuff
They won't fix the thing because they're ordered to do so. It's not a bug, it's a feature.
Fixed in GrapheneOS fwiw
It’s not a bug, it’s a feature.
They've copied gOS's homework one hell of a lot. They clearly don't want to do so here.
This disables the QUIC graceful shutdown feature, and thus closes the leak. The mitigation will persist across reboots, but it may be undone by system updates, in which case the steps will need to be repeated.
Performing this mitigation means that the server-side QUIC socket will remain half-open until it times out, which should generally not negatively affect the Android device or apps running on it. However, only use the command at your own risk if you understand the implications.
does anyone know what are the implications of the fix proposed?
It makes it harder to run big servers talking to android apps. Instead of them saying “I’m done, goodbye” they will just ghost the server. Then the server has to keep a connection open and waiting around to hear from you again even though you are done.
This isn’t a problem if a few people do it, but if everyone does it then servers could end up spending more time waiting on abandoned connections than doing real work.
Well now I'm definitely doing it
However, at the time of writing the issue is marked as inaccessible by Google for unknown reasons.
"Don't be evil"
Hope Lineage and /e/OS implement the fix soon as well
Isn't QUIC long gone, merged into HTTP/3?
This is a most excellent place for technology news and articles.
