Avatar for Username

Search Support

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.

Learn More

Mulongo oyo etiyamaki na archive. Tuna motuna mosusu soki osengeli na lisalisi

Refresh firefox breaks lockpref proxy settings. How to avoid?

  • 1 eyano
  • 1 eza na nkokoso oyo
  • 8 views
  • Eyano yasuka ya adamdroid

adamdroid
adamdroid
more options

As stated. After everything is set up and working, a standard user can go to help, troubleshooting, and refresh firefox, and afterwards are able to bypass locked proxy preference.

I can only speculate why, and hoping someone here has a solution.

Here's things I have tried:

- Locking permissions on various appdata folders. - Checking about:config shows that it should still be enforcing the proxy settings, but for some reason, just isn't.

After I do the refresh, I have yet to find a way to get it to honor the mozilla.cfg file again. It's just completely broken.

This affects only that user profile. Which is why I find it so odd that locking profile ini and install ini and the default profile folder doesn't work. I can't lock the -release profile folder or firefox will believe an instance is already running, and I can't see where inside that profile there might be an issue (this is in the roaming folder, for all I know the issue is in the local folder, but why does firefox need all these folders anyway).

Thanks

As stated. After everything is set up and working, a standard user can go to help, troubleshooting, and refresh firefox, and afterwards are able to bypass locked proxy preference. I can only speculate why, and hoping someone here has a solution. Here's things I have tried: - Locking permissions on various appdata folders. - Checking about:config shows that it should still be enforcing the proxy settings, but for some reason, just isn't. After I do the refresh, I have yet to find a way to get it to honor the mozilla.cfg file again. It's just completely broken. This affects only that user profile. Which is why I find it so odd that locking profile ini and install ini and the default profile folder doesn't work. I can't lock the -release profile folder or firefox will believe an instance is already running, and I can't see where inside that profile there might be an issue (this is in the roaming folder, for all I know the issue is in the local folder, but why does firefox need all these folders anyway). Thanks

Ezalaki modifié na adamdroid

All Replies (1)

adamdroid
adamdroid Nkolo motuna
more options

I guess I have solved it. Refreshing creates a new profile that for some reason does not use properly the mozilla.cfg even when it says it is. I think this is a bug.

Instead it uses only prefs.js in the new profile. If I lock down profile.ini, then close and reopen the browser, it goes back to the old profile and works properly. But still a security issue.

By putting user and prefs js files into the program folder, defaults, prefs subfolder, I am able to stop the initial refresh window from working.

However, I do not think this is completely secure. Standard users can edit the js files that are copied to the new profile, and if they can get those to operate without reloading the browser window, they will have a workaround.

But for my purposes, this is good enough.