Bug 147367 - Firefox ignores network.enableIDN setting
Firefox ignores network.enableIDN setting
Product: Fedora
Classification: Fedora
Component: firefox (Show other bugs)
i686 Linux
medium Severity medium
: ---
: ---
Assigned To: Christopher Aillon
: Security
Depends On:
  Show dependency treegraph
Reported: 2005-02-07 12:46 EST by Ian Pilcher
Modified: 2007-11-30 17:10 EST (History)
4 users (show)

See Also:
Fixed In Version: 1.0.1-1.3.1
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2005-02-25 22:42:46 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

External Trackers
Tracker ID Priority Status Summary Last Updated
Mozilla Foundation 281365 None None None Never

  None (edit)
Description Ian Pilcher 2005-02-07 12:46:26 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.5)
Gecko/20041111 Firefox/1.0

Description of problem:
When network.enableIDN is set to false in about:config, IDN lookups
will initially fail.  When Firefox is stopped and restarted, however,
they will work again, even though the network.enableIDN is still set
to false.

See http://www.shmoo.com/idn/ for an example of how this can be used
for phishing.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1.  Start Mozilla Firefox.
2.  Type "about:config" into the URL bar.
3.  Set network.enableIDN to false.
4.  Visit http://www.shmoo.com/idn/ and click on one of the links;
    lookup will fail (properly).
5.  Close Firefox & restart.
6.  Type "about:config" into URL bar; confirm that network.enableIDN
    is still set to false.
7.  Visit http://www.shmoo.com/idn/ and click on one of the link;
    lookup will succeed.

Actual Results:  IDN lookup succeeds, even though network.enableIDN is
set to false.

Expected Results:  IDN lookup should fail.

Additional info:
Comment 1 Carlos Rodrigues 2005-02-17 10:56:53 EST
This also happens with firefox-1.0-8 from development.
Comment 2 Ian Pilcher 2005-02-25 22:42:46 EST
Appears to be fixed in 1.0.1-1.3.1.
Comment 3 Matthew Miller 2005-02-28 11:02:20 EST
Will there be an errata announcement for the 1.0.1-1.3.1 update?
Comment 4 Christopher Aillon 2005-02-28 12:59:28 EST
I mailed on Saturday.  Whenever someone approves it, yes.
Comment 6 Bill Nottingham 2005-04-19 23:26:58 EDT
*** Bug 143314 has been marked as a duplicate of this bug. ***

Note You need to log in before you can comment on or make changes to this bug.