nsProfileLock::LockWithSymlink should not perform DNS requests when the proxy bypass protection is enabled
Categories
(Toolkit :: Startup and Profile System, defect)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox108 | --- | fixed |
People
(Reporter: pierov, Assigned: pierov)
Details
Attachments
(2 files)
|
1.91 KB,
patch
|
Details | Diff | Splinter Review | |
|
48 bytes,
text/x-phabricator-request
|
Details | Review |
nsProfileLock::LockWithSymlink performs a DNS lookup of the current system hostname, to get the IP address to add it to the symlink name.
We think that if proxy bypass protection is enabled, this function should always use 127.0.0.1.
Basically, the change would be putting the part of code that performs the DNS query under an #ifndef MOZ_PROXY_BYPASS_PROTECTION.
We have had a patch that just removed the DNS query in Tor Browser for many years. It was originally developed by Kathy Brade, who found it could be troublesome when the following conditions are all true:
- The browser profile is on a network file system.
- The file system does not support
fcntl()locking. - The browser is run from two different computers at the same time.
However, we think that honoring MOZ_PROXY_BYPASS_PROTECTION has higher precedence than preventing this scenario.
Thanks!
Comment 1•3 years ago
|
||
The severity field is not set for this bug.
:mossop, could you have a look please?
For more information, please visit auto_nag documentation.
Updated•3 years ago
|
| Assignee | ||
Comment 2•3 years ago
|
||
Hello, I could open a phabricator request with the patch I have already attached.
Could I set you as a reviewer, in case? Otherwise, who could I set?
Thanks in advance!
Comment 3•3 years ago
|
||
(In reply to Pier Angelo Vendrame from comment #2)
Hello, I could open a phabricator request with the patch I have already attached.
Could I set you as a reviewer, in case? Otherwise, who could I set?
Thanks in advance!
Sorry missed this somehow. Yes you can set me as reviewer.
| Assignee | ||
Comment 4•3 years ago
|
||
Instead of using the local computer's IP address within
symlink-based profile lock signatures, always use 127.0.0.1 when the
proxy bypass protection is enabled.
Updated•3 years ago
|
Comment 6•3 years ago
|
||
| bugherder | ||
Description
•