Caută ajutor

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Află mai multe

Acest fir de discuție a fost arhivat. Adresează o întrebare nouă dacă ai nevoie de ajutor.

need to disable Hello functionality at workplace

  • 5 răspunsuri
  • 19 au această problemă
  • 9 vizualizări
  • Ultimul răspuns de cor-el

more options

Need to disable Hello at my workplace. How can this service be blocked with our Web Security Appliance or Firewall?

Need to disable Hello at my workplace. How can this service be blocked with our Web Security Appliance or Firewall?

Soluție aleasă

hi, you could try blocking loop.services.mozilla.com which is the server used for call setup...

Citește acest răspuns în context 👍 2

Toate răspunsurile (5)

more options

Soluție aleasă

hi, you could try blocking loop.services.mozilla.com which is the server used for call setup...

more options

Thanks, will look at blocking that URL.

more options

You can also consider to lock some loop prefs.

//
lockPref("loop.enabled", false);
lockPref("loop.server", "");

Use a mozilla.cfg file in the Firefox program folder to lock prefs or specify new (default) values.

Place a local-settings.js file in the defaults\pref folder where also the channel-prefs.js file is located to specify using mozilla.cfg.

pref("general.config.filename", "mozilla.cfg");
pref("general.config.obscure_value", 0);

These functions can be used in the mozilla.cfg file:

defaultPref();	// set new default value
pref();		// set pref, allow changes in current session
lockPref();	// lock pref, disallow changes

See:

more options

can something like this be use to disable hello locally?

more options

Can you clarify about what you would try to achieve and to what reply you are referring?

If you would loop.server (https://loop.services.mozilla.com/v0) to an empty string then Firefox won't be able to access the server. This will work for all Firefox profiles that are started via the Firefox installation that has the mozilla.cfg file.


//
lockPref("loop.enabled", false);
lockPref("loop.server", "");