Closed Bug 1411617 Opened 8 years ago Closed 6 years ago

Proxy in Mozilla Maintenance Service

Categories

(Toolkit :: Application Update, defect, P5)

Product:
Toolkit
Component:
Application Update
Version:
56 Branch
Type:
defect

Tracking

()

Status:
RESOLVED INCOMPLETE

People

(Reporter: mandrzej, Unassigned)

Details

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:56.0) Gecko/20100101 Firefox/56.0 Build ID: 20171002220106 Steps to reproduce: Just install Firefox with default settings. Your computers work in organisation where proxy is required to surf the Internet. Actual results: Lack of proxy settings for Mozilla Maintenance Service (MMS) cause a lot of traffic which is dropped on firewall. It is important when you have a lot of computers in organisation running Firefox. Now, when MMS starts, it generates UDP question and answer, next SYN packet is sent (with retrasmissions) but it is dropped on firewall. Expected results: Maintenance Service is useful service, however it would be very helpful if it were possibility to input organisation proxy details.
Component: Untriaged → Application Update
Product: Firefox → Toolkit
Can you provide details as to what the Mozilla Maintenance Service is connecting to? The maintenance service intentionally doesn't have any code that attempts to connect to the internet so this is possibly Windows doing this.
Flags: needinfo?(mandrzej)
Priority: -- → P5
Mozilla Maintenance Service (maintenanceservice.exe) is trying to connect with 88.220.177.153, 88.220.177.153, 93.184.220.29, 66.225.197.197. These results come from tcpvcon and wireshark. The best way to reproduce is to install previous release of firefox (branch 55) on fresh Windows installation. Next you should start Firefox twice, becuase the second start will launch Mozilla Maintenance Service.
Flags: needinfo?(mandrzej)
Using both tcpvcon and tcpview I didn't have any connections made by maintenanceservice.exe which is the Mozilla Maintenance Service. It is possible that you have a process that is attaching to the maintenanceservice.exe process causing this since we don't have any networking code in the maintenance service.

Based on comment #4 this can't be the maintenanceservice.exe so resolving incomplete

Status: UNCONFIRMED → RESOLVED
Closed: 6 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.