X
Tippen Sie hierhin, um die Version dieser Website für Mobilgeräte aufzurufen.

Hilfeforum

The most recent update for #Firefox has a "bug fix" (1565315) for which the access to details are denied. Why?

Veröffentlicht

Hi there The most recent update for #Firefox has a "bug fix" (1565315) for which the access to details are denied. That's peculiar for an open source project. The bug is about Russian users having their default search engine changed. Is this just a geolock? VPN didn't work. I like to be able to view the details of any update I'm installing, for obvious privacy reasons. When will these details be made available so I can update? Thanks.

Hi there The most recent update for #Firefox has a "bug fix" (1565315) for which the access to details are denied. That's peculiar for an open source project. The bug is about Russian users having their default search engine changed. Is this just a geolock? VPN didn't work. I like to be able to view the details of any update I'm installing, for obvious privacy reasons. When will these details be made available so I can update? Thanks.
Angefügte Screenshots

Ausgewählte Lösung

Bugs relating to search engines and contracts are necessarily private. Nothing nefarious is going on, as you can tell from the checkin

Diese Antwort im Kontext lesen 1
Zitieren

Mehr Details zum System

Anwendung

  • User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:68.0) Gecko/20100101 Firefox/68.0

Weitere Informationen

jscher2000
  • Top 10 Contributor
8568 Lösungen 70051 Antworten
Veröffentlicht

I don't know if/when that bug will be opened up.

However, I can look at the changes made in the source code in relation to that bug. I found this file, I can't be sure it's the only one:

https://hg.mozilla.org/releases/mozilla-release/rev/1b4e2273cd298414563d0b97295a342e99022bab

Those changes set Yandex (English) as the default search engine in English-language builds of Firefox used in KZ, BY, RU, and TR.

See also: https://www.reddit.com/r/firefox/comments/cf49ro/yandex_became_default_search_engine_after_6801/

I don't know if/when that bug will be opened up. However, I can look at the changes made in the source code in relation to that bug. I found this file, I can't be sure it's the only one: https://hg.mozilla.org/releases/mozilla-release/rev/1b4e2273cd298414563d0b97295a342e99022bab Those changes set Yandex (English) as the default search engine in English-language builds of Firefox used in KZ, BY, RU, and TR. See also: https://www.reddit.com/r/firefox/comments/cf49ro/yandex_became_default_search_engine_after_6801/
Hat Ihnen das weitergeholfen?
Zitieren
cor-el
  • Top 10 Contributor
  • Moderator
17334 Lösungen 156710 Antworten
Veröffentlicht
See also: *https://hg.mozilla.org/mozilla-central/pushloghtml?changeset=ea633a73ac3b6a1d69716659766350a1f4fd3e7e
Hat Ihnen das weitergeholfen?
Zitieren

Fragesteller

Thank you for the additional information. Can you tell us why the bug is concealed? Can you tell us who submitted the bug request?

I can't do an update containing a sealed bug fix, and honestly, no one should. But this puts us at risk. Who needs to be lobbied to open the details of this bugfix?

Thank you for the additional information. Can you tell us why the bug is concealed? Can you tell us who submitted the bug request? I can't do an update containing a sealed bug fix, and honestly, no one should. But this puts us at risk. Who needs to be lobbied to open the details of this bugfix?
Hat Ihnen das weitergeholfen?
Zitieren
jscher2000
  • Top 10 Contributor
8568 Lösungen 70051 Antworten
Veröffentlicht

These questions are beyond the scope of this support forum. Here is the documentation on Mozilla's Bugzilla system: https://developer.mozilla.org/docs/Mozilla/Bugzilla

These questions are beyond the scope of this support forum. Here is the documentation on Mozilla's Bugzilla system: https://developer.mozilla.org/docs/Mozilla/Bugzilla
Hat Ihnen das weitergeholfen?
Zitieren

Fragesteller

jscher2000 said

These questions are beyond the scope of this support forum. Here is the documentation on Mozilla's Bugzilla system: https://developer.mozilla.org/docs/Mozilla/Bugzilla

With whom does this scope fall under? Am I wrong in questioning an obfuscated bug fix? You found SOME changes in the source code related to this but admitted that there could be others. I'm sure you understand that in the current climate, it is pretty suspicious to obfuscate the details of a bug relating to Russia. I would think every dev of an open source project would be concerned about this and looking for answers.

I will not be updating firefox until this is resolved, so who do I need to contact to have these questions answered. I love Firefox and the Mozilla community, but this is concerning to me.

And again, thank you for your replies.

''jscher2000 [[#answer-1239012|said]]'' <blockquote> These questions are beyond the scope of this support forum. Here is the documentation on Mozilla's Bugzilla system: https://developer.mozilla.org/docs/Mozilla/Bugzilla </blockquote> With whom does this scope fall under? Am I wrong in questioning an obfuscated bug fix? You found SOME changes in the source code related to this but admitted that there could be others. I'm sure you understand that in the current climate, it is pretty suspicious to obfuscate the details of a bug relating to Russia. I would think every dev of an open source project would be concerned about this and looking for answers. I will not be updating firefox until this is resolved, so who do I need to contact to have these questions answered. I love Firefox and the Mozilla community, but this is concerning to me. And again, thank you for your replies.
Hat Ihnen das weitergeholfen?
Zitieren
jscher2000
  • Top 10 Contributor
8568 Lösungen 70051 Antworten
Veröffentlicht

Based on cor-el's link and my earlier, the title of the bug is "Fix Yandex missing from en builds when in Russian regions." So I think the file I found shows the relevant changes.

What it does is set Yandex (English) as the default search engine for users in those four countries. Of course, you can change your default search engine after that in the usual way if you are in one of those countries. (Change your default search settings in Firefox)

I don't have time today to read the Bugzilla documentation and figure out who to contact. That is why I gave you the link. Or you can research it going through the Bugzilla home page.

Based on cor-el's link and my earlier, the title of the bug is "Fix Yandex missing from en builds when in Russian regions." So I think the file I found shows the relevant changes. What it does is set Yandex (English) as the default search engine for users in those four countries. Of course, you can change your default search engine after that in the usual way if you are in one of those countries. ([[Change your default search settings in Firefox]]) I don't have time today to read the Bugzilla documentation and figure out who to contact. That is why I gave you the link. Or you can research it going through the Bugzilla home page.
Hat Ihnen das weitergeholfen?
Zitieren

Fragesteller

Fair enough. I'll see if I can find a contact. But aren't you curious why the details of such a mundane fix would be obfuscated?

I would think, as a dev, you'd be even more curious than I. Don't you want to find out more about this bug? Exactly what was injected into the code? Who made the decision to "classify" this code in an open source project?

I find all of this fishy, against the ethos of open source and Mozilla's usual stance.

Thanks for your time.

Fair enough. I'll see if I can find a contact. But aren't you curious why the details of such a mundane fix would be obfuscated? I would think, as a dev, you'd be even more curious than I. Don't you want to find out more about this bug? Exactly what was injected into the code? Who made the decision to "classify" this code in an open source project? I find all of this fishy, against the ethos of open source and Mozilla's usual stance. Thanks for your time.
Hat Ihnen das weitergeholfen?
Zitieren
jscher2000
  • Top 10 Contributor
8568 Lösungen 70051 Antworten
Veröffentlicht

Oh, I'm not a Firefox dev. Most support forum volunteers are users like you who spend a lot of time learning about Firefox.

Oh, I'm not a Firefox dev. Most support forum volunteers are users like you who spend a lot of time learning about Firefox.
Hat Ihnen das weitergeholfen?
Zitieren

Fragesteller

Sorry for mislabeling you... but still, all the same questions apply, lol.

Have a good one and thanks for contributing like you do.

Sorry for mislabeling you... but still, all the same questions apply, lol. Have a good one and thanks for contributing like you do.
Hat Ihnen das weitergeholfen?
Zitieren
Tyler Downer
  • Top 25 Contributor
  • Moderator
1525 Lösungen 10617 Antworten
Veröffentlicht

Ausgewählte Lösung

Bugs relating to search engines and contracts are necessarily private. Nothing nefarious is going on, as you can tell from the checkin

Bugs relating to search engines and contracts are necessarily private. Nothing nefarious is going on, as you can tell from the checkin
Hat Ihnen das weitergeholfen? 1
Zitieren

Fragesteller

Tyler Downer said

Bugs relating to search engines and contracts are necessarily private. Nothing nefarious is going on, as you can tell from the checkin

Thank you for your reply Tyler. This makes sense that Mozilla entered into a contract with Yandex (or whoever) to make their search engine the default. Thanks for clearing that up for me. It is appreciated. I only brought the issue up because I support Mozilla's open and transparent nature.

''Tyler Downer [[#answer-1239612|said]]'' <blockquote> Bugs relating to search engines and contracts are necessarily private. Nothing nefarious is going on, as you can tell from the checkin </blockquote> Thank you for your reply Tyler. This makes sense that Mozilla entered into a contract with Yandex (or whoever) to make their search engine the default. Thanks for clearing that up for me. It is appreciated. I only brought the issue up because I support Mozilla's open and transparent nature.
Hat Ihnen das weitergeholfen?
Zitieren
Stellen Sie eine Frage

Sie müssen sich mit Ihrem Benutzerkonto anmelden, um auf Beiträge zu antworten. Bitte stellen Sie eine neue Frage, wenn Sie noch kein Benutzerkonto haben.