搜尋 Mozilla 技術支援網站

防止技術支援詐騙。我們絕對不會要求您撥打電話或發送簡訊,或是提供個人資訊。請用「回報濫用」功能回報可疑的行為。

Learn More

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

  • 11 回覆
  • 1 有這個問題
  • 2 次檢視
  • 最近回覆由 user1537567

more options

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.
附加的畫面擷圖

被選擇的解決方法

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

從原來的回覆中察看解決方案 👍 1

所有回覆 (11)

more options

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/

more options
more options

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?

more options

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

more options

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.

more options

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.

more options

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.

more options

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

more options

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

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

more options

選擇的解決方法

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

more options

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.