搜尋 Mozilla 技術支援網站

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

了解更多

why does it open so many ports?

  • 2 回覆
  • 1 有這個問題
  • 43 次檢視
  • 最近回覆由 cor-el

more options

i understand add-ons open connections.. but why does FF itself need 8 ports opened? if i was hack i would def target these. TCP 1100 and upwards.. then i just piggyback on the traffic. There is no need for this many port openings. and every time you close their connection.. boom.. they reopen on a diff port range. This is a major vulnerability.

i understand add-ons open connections.. but why does FF itself need 8 ports opened? if i was hack i would def target these. TCP 1100 and upwards.. then i just piggyback on the traffic. There is no need for this many port openings. and every time you close their connection.. boom.. they reopen on a diff port range. This is a major vulnerability.

被選擇的解決方法

Firefox needs to open ports to communicate with other Firefox processes.

You may see three or more Firefox processes running.

  • one process for the main Firefox thread (user interface)
  • one or more content processes set via dom.ipc.processCount
    Options/Preferences -> General -> Performance
    remove checkmark: [ ] "Use recommended performance settings"
  • one process for the compositor thread (Windows;graphics)

You can find the current multi-process state on the Troubleshooting Information (about:support) page.

  • "Help -> Troubleshooting Information" -> "Application Basics":
    Multiprocess Windows
    Web Content Processes
從原來的回覆中察看解決方案 👍 0

所有回覆 (2)

more options

If you are aware of a way to exploit those open ports, please file a bug report: https://bugzilla.mozilla.org/

To reduce the number of background connections, see: How to stop Firefox from making automatic connections.

more options

選擇的解決方法

Firefox needs to open ports to communicate with other Firefox processes.

You may see three or more Firefox processes running.

  • one process for the main Firefox thread (user interface)
  • one or more content processes set via dom.ipc.processCount
    Options/Preferences -> General -> Performance
    remove checkmark: [ ] "Use recommended performance settings"
  • one process for the compositor thread (Windows;graphics)

You can find the current multi-process state on the Troubleshooting Information (about:support) page.

  • "Help -> Troubleshooting Information" -> "Application Basics":
    Multiprocess Windows
    Web Content Processes