Menu
Our current plan is to disable HTTP3 to mitigate until we can locate the exact bug in the networking stack.” “Telemetry was first implicated because it’s one of the first services a normal Firefox configuration will connect to, but presumably the bug will trigger with any other connection to such a server (so disabling telemetry is pointless). “Our current suspicion is that a cloud provider or load balancer that fronts one of our own servers got an update that triggers an existing HTTP3 bug”, Gian-Carlo Pascutto, a security engineering manager at Mozilla, wrote.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |